From: Jean Delvare <khali@linux-fr.org>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Zhang Rui <rui.zhang@intel.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next:als tree build failure
Date: Thu, 28 Jan 2010 13:45:18 +0100 [thread overview]
Message-ID: <20100128134518.26b762ed@hyperion.delvare> (raw)
In-Reply-To: <4B618412.30704@cam.ac.uk>
On Thu, 28 Jan 2010 12:33:22 +0000, Jonathan Cameron wrote:
> On 01/28/10 12:17, Stephen Rothwell wrote:
> > Hi Jonathan, Jean,
> >
> > On Thu, 28 Jan 2010 11:59:37 +0000 Jonathan Cameron <jic23@cam.ac.uk> wrote:
> >>
> >> It does make sense to keep these two steps separate. Ah well, I guess any
> >> work around would be a pretty terrible cludge. I'll roll these two patches
> >> back together and otherwise we will end up with something even less coherent.
> >
> > OK, thanks guys.
> >
> Everything should now be fixed in the als tree. New version of the move commit
> cleans out the i2c/chips directory and changes the i2c/Makefile and i2c/Kconfig
> appropriately. Only remaining related elements are the debug Kconfig option for
> i2c/chips but that can definitely go through the i2c tree rather than als (if there
> are no other users) and shouldn't break any builds.
I'll take care of the debug option later, no problem.
--
Jean Delvare
prev parent reply other threads:[~2010-01-28 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:23 linux-next:als tree build failure Stephen Rothwell
2010-01-28 7:41 ` Jean Delvare
2010-01-28 11:59 ` Jonathan Cameron
2010-01-28 12:17 ` Stephen Rothwell
2010-01-28 12:33 ` Jonathan Cameron
2010-01-28 12:45 ` Jean Delvare [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=20100128134518.26b762ed@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).