From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: FUJITA Tomonori <tomof@acm.org>,
James.Bottomley@SteelEye.com, torvalds@linux-foundation.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2
Date: Tue, 7 Aug 2007 10:47:20 -0700 [thread overview]
Message-ID: <20070807104720.d4b238b6.akpm@linux-foundation.org> (raw)
In-Reply-To: <46B87FDE.3050309@garzik.org>
On Tue, 07 Aug 2007 10:21:18 -0400 Jeff Garzik <jeff@garzik.org> wrote:
> FUJITA Tomonori wrote:
> > On Tue, 7 Aug 2007 00:14:29 -0700
> > Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> >> On Mon, 06 Aug 2007 22:55:41 -0500 James Bottomley <James.Bottomley@SteelEye.com> wrote:
> >>
> >>> The real root cause of all of this is that there's no tree I can
> >>> persuade all the interested parties to test that includes all of these
> >>> features. In spite of the fact they've all been incubating in -mm for
> >>> at least 3 months, no-one apparently tested all the features together
> >>> until 2.6.23-rc1 was released, so then we're scrambling to address the
> >>> issues as they arise.
> >> I pulled git-scsi-misc on July 19 and there was no bsg code in there at
> >> all. I pulled again on July 20 and all the bsg code was in mainline. So
> >> it appears that the bsg code went mailing-list -> mainline in less than 24
> >> hours, so there wasn't a lot of opportunity for -mm testing there.
> >
> > bsg was merged via Jens' branch. After that, I asked James to send
> > some fixes via the scsi-rc-fixes.
>
> ISTR that Jens doesn't regularly push / get picked up by -mm? That
> seems like an easy problem to solve.
>
-mm includes
git+ssh://master.kernel.org/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git#for-akpm,
but it's up to Jens to choose what goes in there.
git-block has been dropped from -mm since 2.6.23-rc1-mm1 (I think) because
it has something in there which breaks sata on the Vaio. Prior to that (in
2.6.22-rc-late) there was nothing in that tree.
next prev parent reply other threads:[~2007-08-07 17:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 17:31 [GIT PATCH] scsi bug fixes for 2.6.23-rc2 James Bottomley
2007-08-07 0:51 ` Linus Torvalds
2007-08-07 3:55 ` James Bottomley
2007-08-07 4:01 ` Linus Torvalds
2007-08-07 13:12 ` James Smart
2007-08-07 16:13 ` Jeff Garzik
2007-08-07 14:31 ` James Bottomley
2007-08-07 16:20 ` Jeff Garzik
2007-08-07 16:31 ` James Bottomley
2007-08-07 7:14 ` Andrew Morton
2007-08-07 13:58 ` FUJITA Tomonori
2007-08-07 14:21 ` Jeff Garzik
2007-08-07 17:47 ` Andrew Morton [this message]
2007-08-07 14:25 ` James Bottomley
2007-08-07 14:55 ` Alan Cox
2007-08-07 14:56 ` Jeff Garzik
2007-08-07 15:11 ` Jeff Garzik
2007-08-07 15:38 ` James Bottomley
2007-08-07 15:43 ` Jeff Garzik
2007-08-07 17:51 ` Andrew Morton
2007-08-13 12:42 ` Jens Axboe
2007-08-13 15:58 ` Jeff Garzik
2007-08-13 18:02 ` Jens Axboe
2007-08-13 18:07 ` Jens Axboe
2007-08-07 15:24 ` Jeff Garzik
2007-08-07 14:53 ` Rene Herman
2007-08-07 16:06 ` Jeff Garzik
2007-08-07 16:27 ` James Smart
2007-08-07 16:34 ` Jeff Garzik
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=20070807104720.d4b238b6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@SteelEye.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tomof@acm.org \
--cc=torvalds@linux-foundation.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