From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
Mike Christie <michaelc@cs.wisc.edu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jayamohan Kallickal <jayamohank@serverengines.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (scsi-post-merge tree related)
Date: Mon, 2 Aug 2010 20:51:25 -0400 [thread overview]
Message-ID: <201008022051.26695.konrad@kernel.org> (raw)
In-Reply-To: <1280780042.2843.628.camel@mulgrave.site>
> > 2). Reviewed-by: Konrad Rzeszutek Wilk <konrad@kernel.org> for the
> > the part that puts in drivers/scsi and will make it now under James'
> > mainternship.
> >
> > James,
> >
> > I've asked Linus to pull my iBFT tree before yours as there was this
> > dependency. Are you OK putting this patch in your tree, or would you
> > prefer that I expunge Mike's patch from mine?
>
> I can put this patch into my post merge tree. I suspect you having a
> post-post-merge tree (needed for the build problems) might be a bit
> overkill ...
>
> James
OK. Thanks.
next prev parent reply other threads:[~2010-08-03 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 16:44 linux-next: build failure after merge of the final tree (scsi-post-merge tree related) Stephen Rothwell
2010-08-02 16:47 ` Stephen Rothwell
2010-08-02 16:54 ` James Bottomley
2010-08-02 17:46 ` Mike Christie
2010-08-02 18:59 ` Konrad Rzeszutek Wilk
2010-08-02 19:09 ` Mike Christie
2010-08-02 19:59 ` Konrad Rzeszutek Wilk
2010-08-02 20:14 ` James Bottomley
2010-08-03 0:51 ` Konrad Rzeszutek Wilk [this message]
2010-08-05 1:55 ` Stephen Rothwell
2010-08-02 16:59 ` Mike Christie
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=201008022051.26695.konrad@kernel.org \
--to=konrad@kernel.org \
--cc=James.Bottomley@suse.de \
--cc=jayamohank@serverengines.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=randy.dunlap@oracle.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 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.