On Thu, Aug 11, 2011 at 03:43:09PM +0200, Takashi Iwai wrote:

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@blackfin.uclinux.org [mailto:uclinux-dist-devel-bounces@blackfin.uclinux.org] On Behalf Of Scott Jiang Sent: Thursday, August 11, 2011 4:27 PM To: Greg Kroah-Hartman Cc: uclinux-dist-devel@blackfin.uclinux.org; alsa-devel@alsa-project.org; stable@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 already?

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 suppose.

Scott, the patch to stable kernel must have been applied to the upstream tree beforehand. Read Documentation/stable_kernel_rules.txt.

Ok, now dropped from my stable "to-apply" mbox.

I'll wait for the real patch to hit Linus's tree.

greg k-h

2011/8/11 Takashi Iwai tiwai@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@blackfin.uclinux.org [mailto:uclinux-dist-devel-bounces@blackfin.uclinux.org] On Behalf Of Scott Jiang Sent: Thursday, August 11, 2011 4:27 PM To: Greg Kroah-Hartman Cc: uclinux-dist-devel@blackfin.uclinux.org; alsa-devel@alsa-project.org; stable@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 already?

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 suppose.

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?

Scott

[dropped Cc to stable kernel]

At Fri, 12 Aug 2011 12:10:25 +0800, Scott Jiang wrote:

2011/8/11 Takashi Iwai tiwai@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@blackfin.uclinux.org [mailto:uclinux-dist-devel-bounces@blackfin.uclinux.org] On Behalf Of Scott Jiang Sent: Thursday, August 11, 2011 4:27 PM To: Greg Kroah-Hartman Cc: uclinux-dist-devel@blackfin.uclinux.org; alsa-devel@alsa-project.org; stable@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 already?

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 suppose.

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.

To make sure, it doesn't mean to send the patch to stable tree. See below.

I have a question here that patch for 3.1 and 3.0 is different, who is responsible for the back patch?

A slight fuzz can be resolved by patch program. I guess 3.1 patch is applicable to 3.0 in your case.

Just try to apply the same patch to 3.0 before submission. If it's applied without error, put "Cc: stable@kernel.org" line after your Signed-off-by line in the change log text. When this line is added, you don't have to send it via e-mail. Greg will pick it up automatically when it's merged to the Linus tree. This is the preferred way than sending patches individually to stable@kernel.org via e-mail.

Prepare and send e-mail to stable@kernel.org only when 3.1 patch isn't applicable and a different patch is mandatory for 3.0 kernel. This process begins _after_ the patch is merged to Linus tree. In that case, don't forget to give the corresponding upstream commit it of the patch, too.

Takashi

At Fri, 12 Aug 2011 14:33:38 +0900, Mark Brown wrote:

On Fri, Aug 12, 2011 at 07:30:04AM +0200, Takashi Iwai wrote:

...

Scott Jiang wrote:

...

...

I have a question here that patch for 3.1 and 3.0 is different, who is responsible for the back patch?

...

A slight fuzz can be resolved by patch program. I guess 3.1 patch is applicable to 3.0 in your case.

It's not just fuzz, between 3.0 and 3.1 the code was moved into a completely different file.

Ah, I forgot the file split.

Takashi