From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: kgene.kim@samsung.com, heiko@sntech.de, ben-linux@fluff.org,
tiwai@suse.de, linux-next@vger.kernel.org
Subject: Re: linux-next broken by "ARM: S3C2440: move mach-s3c2440/* into mach-s3c24xx/"
Date: Fri, 9 Mar 2012 12:16:22 +0000 [thread overview]
Message-ID: <20120309121621.GH3273@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F590F74.2030007@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Thu, Mar 08, 2012 at 02:58:44PM -0500, Paul Gortmaker wrote:
> The "it" was the commit in the subject, and the ID in the above text.
> That was the last commit to have touched this file (via moving it).
> What I took as a relation to fix/asoc was shown in the text you've
> gone and deleted here in the follow up.
You'd written some text but the text wasn't teribly clear - nothing
about the code looks at all audio bug fix related. Are you sure the
error wasn't just in Linus' tree?
> In any case, it does appear the file was broken before it was moved.
> The offending commit is actually c1ba544f81544ed9613ad5d058968533dbcef4b2
> "ARM: S3C24XX: Fix restart on S3C2442"
> It appears that a closing brace was dropped when it was integrated.
Right, and that commit doesn't appear to be in the ASoC bugfix branch
which is why I was mystified.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-09 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 16:23 linux-next broken by "ARM: S3C2440: move mach-s3c2440/* into mach-s3c24xx/" Paul Gortmaker
2012-03-08 19:12 ` Mark Brown
2012-03-08 19:58 ` Paul Gortmaker
2012-03-08 20:44 ` Heiko Stübner
2012-03-09 12:16 ` Mark Brown [this message]
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=20120309121621.GH3273@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ben-linux@fluff.org \
--cc=heiko@sntech.de \
--cc=kgene.kim@samsung.com \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--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.