From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Ben Dooks <ben@simtec.co.uk>,
Alexander Schulz <alex@shark-linux.de>
Subject: Re: linux-next: manual merge of the sound tree with the arm tree
Date: Wed, 11 Mar 2009 11:24:43 +0000 [thread overview]
Message-ID: <20090311112443.GA7939@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20090311104049.GA14668@flint.arm.linux.org.uk>
On Wed, Mar 11, 2009 at 10:40:49AM +0000, Russell King wrote:
> But, at the end of the day, these things have to be fixed one way or
> other, whether that be by removing the offending commits, by reverting
> the patches, or patching the specific bad changes back to how they
> originally were. I really don't mind which option is taken, just so
> long as the final outcome is the right one.
Let's go with reverting things, then - that avoids having to drop the
audio drivers and the subsequent work that was done on them.
Takashi, here's an initial revert of the two hunks I mentioned
previously - I've not checked the other two hunks yet.
The following changes since commit f455dfb106916d855d59686fe16575c2ceb2cb2a:
Mark Brown (1):
ASoC: Fix up merge with the ARM tree
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git for-2.6.30
Mark Brown (2):
[ARM] Revert extraneous changes from the S3C audio header move
Merge branch 's3c-iis-header' into for-2.6.30
arch/arm/mach-s3c2410/include/mach/hardware.h | 3 +++
arch/arm/mach-shark/include/mach/io.h | 3 +--
2 files changed, 4 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2009-03-11 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 3:45 linux-next: manual merge of the sound tree with the arm tree Stephen Rothwell
2009-03-10 20:04 ` Mark Brown
2009-03-11 0:41 ` Stephen Rothwell
2009-03-11 6:58 ` Takashi Iwai
2009-03-11 8:52 ` Russell King
2009-03-11 9:18 ` Takashi Iwai
2009-03-11 9:41 ` Russell King
2009-03-11 10:02 ` Takashi Iwai
2009-03-11 10:40 ` Russell King
2009-03-11 11:24 ` Mark Brown [this message]
2009-03-11 13:28 ` Takashi Iwai
2009-03-11 22:32 ` Mark Brown
2009-03-12 2:48 ` Stephen Rothwell
2009-03-11 9:49 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2010-07-19 1:00 Stephen Rothwell
2010-07-20 9:03 ` Mark Brown
2010-07-20 20:54 ` Ryan Mallon
2010-07-22 1:28 Stephen Rothwell
2010-07-22 6:18 ` Takashi Iwai
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=20090311112443.GA7939@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alex@shark-linux.de \
--cc=ben@simtec.co.uk \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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.