From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Robert Jennings <rcj@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: scsi tree build failure
Date: Tue, 08 Jul 2008 08:48:42 +1000 [thread overview]
Message-ID: <1215470922.8970.150.camel@pasglop> (raw)
In-Reply-To: <1215468479.3274.42.camel@localhost.localdomain>
On Mon, 2008-07-07 at 17:07 -0500, James Bottomley wrote:
> I thought it was all done and dusted (which is why I put it in
> scsi-misc). However, now Brian King seems to have some late arriving
> comments.
There are comments on the whole serie yup, I haven't put it in the
tree yet.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-scsi <linux-scsi@vger.kernel.org>,
linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: linux-next: scsi tree build failure
Date: Tue, 08 Jul 2008 08:48:42 +1000 [thread overview]
Message-ID: <1215470922.8970.150.camel@pasglop> (raw)
In-Reply-To: <1215468479.3274.42.camel@localhost.localdomain>
On Mon, 2008-07-07 at 17:07 -0500, James Bottomley wrote:
> I thought it was all done and dusted (which is why I put it in
> scsi-misc). However, now Brian King seems to have some late arriving
> comments.
There are comments on the whole serie yup, I haven't put it in the
tree yet.
Cheers,
Ben.
next prev parent reply other threads:[~2008-07-07 22:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 12:25 linux-next: scsi tree build failure Stephen Rothwell
2008-07-07 12:25 ` Stephen Rothwell
2008-07-07 14:39 ` James Bottomley
2008-07-07 14:39 ` James Bottomley
2008-07-07 14:53 ` Robert Jennings
2008-07-07 14:53 ` Robert Jennings
2008-07-07 22:05 ` Benjamin Herrenschmidt
2008-07-07 22:05 ` Benjamin Herrenschmidt
2008-07-07 22:07 ` James Bottomley
2008-07-07 22:07 ` James Bottomley
2008-07-07 22:48 ` Benjamin Herrenschmidt [this message]
2008-07-07 22:48 ` Benjamin Herrenschmidt
2008-07-07 22:00 ` Benjamin Herrenschmidt
2008-07-07 22:00 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-10-15 6:49 Stephen Rothwell
2008-10-15 12:27 ` James Bottomley
2008-12-15 14:37 Stephen Rothwell
2008-12-15 14:52 ` James Bottomley
2008-12-17 12:20 ` Stephen Rothwell
2008-12-21 3:30 ` Stephen Rothwell
2008-12-22 1:59 ` James Bottomley
2008-12-22 2:38 ` Stephen Rothwell
2008-12-30 16:16 Stephen Rothwell
2008-12-30 16:30 ` James Bottomley
2009-03-16 10:39 Stephen Rothwell
2009-03-16 13:22 ` James Bottomley
2009-04-02 5:49 Stephen Rothwell
2009-04-02 14:22 ` James Bottomley
2009-04-02 17:19 ` Robert Love
2009-04-02 18:23 ` James Bottomley
2009-04-03 0:26 ` Stephen Rothwell
2009-04-03 1:16 ` James Bottomley
2009-04-03 2:37 ` Stephen Rothwell
2009-06-15 2:17 Stephen Rothwell
2009-06-15 15:11 ` James Bottomley
2009-06-15 21:40 ` Benjamin Herrenschmidt
2009-06-16 2:24 ` James Bottomley
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=1215470922.8970.150.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rcj@linux.vnet.ibm.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.