[alsa-devel] [uclinux-dist-devel] [PATCH 3.0]ASoC: ad193x: add spi_hw_read, fix sysclk and register definition
scott.jiang.linux at gmail.com
Fri Aug 12 06:10:25 CEST 2011
2011/8/11 Takashi Iwai <tiwai at suse.de>:
> At Thu, 11 Aug 2011 06:34:32 -0700,
> Greg KH wrote:
>> On Thu, Aug 11, 2011 at 04:52:18AM -0400, Zhang, Sonic wrote:
>> > >-----Original Message-----
>> > >From: uclinux-dist-devel-bounces at blackfin.uclinux.org
>> > >[mailto:uclinux-dist-devel-bounces at blackfin.uclinux.org] On
>> > >Behalf Of Scott Jiang
>> > >Sent: Thursday, August 11, 2011 4:27 PM
>> > >To: Greg Kroah-Hartman
>> > >Cc: uclinux-dist-devel at blackfin.uclinux.org;
>> > >alsa-devel at alsa-project.org; stable at kernel.org
>> > >Subject: [uclinux-dist-devel] [alsa-devel][PATCH 3.0]ASoC:
>> > >ad193x: add spi_hw_read, fix sysclk and register definition
>> > >
>> > >asoc cache layer can't support this kind of spi registers, so
>> > >bypass cache and read regiters directly
>> > >
>> > This patch is against stable kernel 3.0 only, the ASOC framework in kernel 3.1 and later are different.
>> Then I need some acks from all of the relevant maintainers before I can
>> apply it to the stable kernel tree.
>> Is there a corrisponding patch in Linus's tree that does the same thing
> Not yet, even neither in sound git tree.
> We're handling the same patch now for 3.1. As the patch is likely
> applicable to 3.0 as is, putting Cc to stable would be enough, I
> Scott, the patch to stable kernel must have been applied to the
> upstream tree beforehand. Read Documentation/stable_kernel_rules.txt.
Thanks, Takashi. I should send patch for 3.1 and cc stable tree.
I have a question here that patch for 3.1 and 3.0 is different, who is
responsible for the back patch?
More information about the Alsa-devel