public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>
Subject: Re: linux-next: i2c tree build failure
Date: Mon, 31 Aug 2009 21:03:35 +1000	[thread overview]
Message-ID: <20090831210335.f382d7ff.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090831120449.3f64aa74@hyperion.delvare>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

Hi Jean,

On Mon, 31 Aug 2009 12:04:49 +0200 Jean Delvare <khali@linux-fr.org> wrote:
> 
> These are caused by the fact that I moved the patch adding
> class_compat_create_link() and friends out of the NEXT_PATCHES section.
> I did so because Greg KH (Cc'd) added this patch to his driver-core
> patch set, which I thought was part of linux-next. I simply didn't want
> to apply the same patch twice.

It doesn't really matter if the same patch appears twice - git usually
copes quite well.  Also I can tell and I (usually) don't bother
commenting on it.

> To clarify the dependency, I added the following to my series.conf:
> 
> # NEXT_BASE driver-core.current
> 
> but apparently it didn't work as intended.
> 
> Greg, please clarify whether the patch in question
> (driver-core-add-support-for-compatibility-classes.patch) is pushed to
> linux-next or not.
> 
> Stephen, if my dependency tag is not correct, please tell me how to fix
> it.

It was fine, except that Greg has that patch in the driver-core series
(not driver-core.current).  It you decide to leave that patch out and
change the dependency, please let me know as I will then have to merge
your tree after Greg's (it is currently earlier.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-08-31 11:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  1:19 linux-next: i2c tree build failure Stephen Rothwell
2009-08-31 10:04 ` Jean Delvare
2009-08-31 11:03   ` Stephen Rothwell [this message]
2009-08-31 11:16     ` Jean Delvare
2009-08-31 11:59       ` Stephen Rothwell
2009-08-31 12:15         ` Jean Delvare
2009-08-31 12:21           ` Stephen Rothwell

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=20090831210335.f382d7ff.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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