From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Greg KH <greg@kroah.com>,
Scott Jiang <scott.jiang.linux@gmail.com>,
"Zhang, Sonic" <Sonic.Zhang@analog.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>
Subject: Re: [uclinux-dist-devel] [PATCH 3.0]ASoC: ad193x: add spi_hw_read, fix sysclk and register definition
Date: Fri, 12 Aug 2011 07:38:33 +0200 [thread overview]
Message-ID: <s5hfwl7xk86.wl%tiwai@suse.de> (raw)
In-Reply-To: <20110812053335.GA13521@opensource.wolfsonmicro.com>
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
next prev parent reply other threads:[~2011-08-12 5:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 8:26 [PATCH 3.0]ASoC: ad193x: add spi_hw_read, fix sysclk and register definition Scott Jiang
[not found] ` <CAHG8p1B2HB61yooEsPwzw+4E60ffM2NUsb98yCsanfPnWD9vgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-11 8:52 ` [alsa-devel][PATCH " Zhang, Sonic
2011-08-11 13:34 ` [uclinux-dist-devel] [PATCH " Greg KH
2011-08-11 13:43 ` Takashi Iwai
2011-08-11 14:17 ` [stable] " Greg KH
2011-08-12 2:44 ` Mark Brown
2011-08-12 4:10 ` Scott Jiang
2011-08-12 4:17 ` Mark Brown
2011-08-12 5:30 ` Takashi Iwai
2011-08-12 5:33 ` Mark Brown
2011-08-12 5:38 ` Takashi Iwai [this message]
2011-08-12 2:42 ` Barry Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hfwl7xk86.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Sonic.Zhang@analog.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=greg@kroah.com \
--cc=scott.jiang.linux@gmail.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.