From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: kgene.kim@samsung.com
Cc: ben-linux@fluff.org, tiwai@suse.de, linux-next@vger.kernel.org
Subject: linux-next broken by "ARM: S3C2440: move mach-s3c2440/* into mach-s3c24xx/"
Date: Thu, 8 Mar 2012 11:23:26 -0500 [thread overview]
Message-ID: <20120308162326.GA30941@windriver.com> (raw)
Something bad happened in this commit (dd6f01b5cc). It looks like
the moved file is truncated, causing this failure:
http://kisskb.ellerman.id.au/kisskb/buildresult/5818815/
I believe it came in via the fix/asoc tree.
Paul.
--
paul@yow-lpgnfs-02:~/git/linux-head$ git show `git rev-list --merges dd6f01b5cc..mar8|tail -n1`
commit 79ad0a5e9210b165c62e269eb48ade9361c630f3
Merge: 94a8d5c 539d3d8
Author: Takashi Iwai <tiwai@suse.de>
Date: Thu Sep 24 09:16:15 2009 +0200
Merge branch 'fix/asoc' into for-next
paul@yow-lpgnfs-02:~/git/linux-head$
next reply other threads:[~2012-03-08 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 16:23 Paul Gortmaker [this message]
2012-03-08 19:12 ` linux-next broken by "ARM: S3C2440: move mach-s3c2440/* into mach-s3c24xx/" Mark Brown
2012-03-08 19:58 ` Paul Gortmaker
2012-03-08 20:44 ` Heiko Stübner
2012-03-09 12:16 ` 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=20120308162326.GA30941@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-next@vger.kernel.org \
--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.