Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Ben Dooks <ben-alsa@fluff.org>, alsa-devel@alsa-project.org
Subject: Re: [patch 0/9] S3C24XX/S3C64XX updates
Date: Thu, 05 Mar 2009 11:36:34 +0100	[thread overview]
Message-ID: <s5h8wnk45ot.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090305103111.GA2416@sirena.org.uk>

At Thu, 5 Mar 2009 10:31:12 +0000,
Mark Brown wrote:
> 
> On Thu, Mar 05, 2009 at 08:23:25AM +0100, Takashi Iwai wrote:
> 
> > Me too :)  I wouldn't take this for 2.6.29 as long as it builds now,
> > but this particular change should go through ARM tree, so it's rather
> > Russell's call.  Could you forward this one?
> 
> > The others are applied fine to sound tree as 2.6.30 changes.
> 
> Ordinarily it should go through the ARM tree but due to the addition of
> the S3C64xx support it would create merge issues to separate it out -
> most of the other patches in the series depend on this in one way or
> another.  Ben is the maintainer for the general Samsung processor
> support and this header move is part of a general reorgansation of ARM
> headers from include/asm-arm into arch/arm so it was expected and should
> be entirely uncontrovesial.

Fair enough.

> I could separate it out and push a separate branch via Russell as well
> but that'd make more work for him and he's been having some very bad
> network problems in addition to all the stuff he normally has to do so
> I'm not sure he'd welcome more work right now.

Then it must be OK to keep the changes in our tree.  Though, it'd be
nice to have Russell's ack beforehand.
Maybe we can separate the header-move patch to another branch so that
he can pull it in easily if needed.


thanks,

Takashi

  reply	other threads:[~2009-03-05 10:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  0:49 [patch 0/9] S3C24XX/S3C64XX updates Ben Dooks
2009-03-04  0:49 ` [patch 1/9] S3C24XX: Move and update IIS headers Ben Dooks
2009-03-04  0:49 ` [patch 2/9] JIVE: Add ASoC audio support Ben Dooks
2009-03-04 14:57   ` Mark Brown
2009-03-04  0:49 ` [patch 3/9] S3C: Move <mach/audio.h> to <plat/audio.h> Ben Dooks
2009-03-04  0:49 ` [patch 4/9] S3C24XX ASoC: Fix copyright statements on Simtec files Ben Dooks
2009-03-04 19:20   ` Mark Brown
2009-03-04  0:49 ` [patch 5/9] S3C: Split s3c2412-i2s.c into core and SoC specific parts Ben Dooks
2009-03-04 19:52   ` Mark Brown
2009-03-04  0:49 ` [patch 6/9] S3C64XX: Add s3c64xx-i2s support Ben Dooks
2009-03-04  0:56   ` Ben Dooks
2009-03-04 19:56   ` Mark Brown
2009-03-04  0:49 ` [patch 7/9] ASoC: Ensure codec check hw_write error at probe Ben Dooks
2009-03-04 19:57   ` Mark Brown
2009-03-04  0:49 ` [patch 8/9] SMDK6410: Add support for WM8731 on an add-on board Ben Dooks
2009-03-04 20:06   ` Mark Brown
2009-03-04  0:49 ` [patch 9/9] AUDIO: Select DMA if I2S is configured Ben Dooks
2009-03-04 20:29 ` [patch 0/9] S3C24XX/S3C64XX updates Mark Brown
2009-03-05  7:23   ` Takashi Iwai
2009-03-05 10:31     ` Mark Brown
2009-03-05 10:36       ` Takashi Iwai [this message]
2009-03-05 11:03         ` Mark Brown
2009-03-11 10:39           ` Ben Dooks
2009-03-11 12:47             ` Mark Brown

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=s5h8wnk45ot.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ben-alsa@fluff.org \
    --cc=broonie@sirena.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox