linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2
Date: Mon, 13 Aug 2007 20:07:57 +0200	[thread overview]
Message-ID: <20070813180757.GZ23758@kernel.dk> (raw)
In-Reply-To: <20070813180212.GY23758@kernel.dk>

On Mon, Aug 13 2007, Jens Axboe wrote:
> On Mon, Aug 13 2007, Jeff Garzik wrote:
> > Jens Axboe wrote:
> > >#for-akpm is usually only in very few -mm release anyway, so it's not
> > >like it would have made much difference. We/you/I need to improve that,
> > >certainly.
> > >
> > >Honestly, for bsg, it wasn't much of an issue. We had build problems
> > >when bsg was merged which was unfortunate but got fixed quickly. Having
> > >bsg in -mm would not have caused any testing of the driver in question
> > >outside of what it already received, given the nature of it.
> > 
> > 
> > That's just an excuse for what happened -- you made an end run around 
> > our test tree.  Pretty please with sugar on it -- make sure changes show 
> > up in -mm.
> 
> It's not just an excuse, there are repeatably problems with getting the
> block stuff pulled into -mm. Sometimes it's my problem, but not always.
> Then I get a note saying that pulling was disabled due to merge
> problems, usually right before -mmX goes out. So it misses that release.

This may sound like I'm blaming Andrew, but that is not my intention. He
does a lot of work and he can't (and should not) attempt to fix every
integration and merge issue. Perhaps if I/we were more strict in pushing
every block bit through the block git tree, it wouldn't be so much of an
integration pain. Then the work would be in me to sort out, which I'm
happy to do.

Then there are things like the sg chaining bits, which touch a lot of
arch code. Those are just painful to deal with, for obvious reasons.
Right now there are not in -mm, but that's because of a bug that
prevents Andrews laptop from booting properly.

-- 
Jens Axboe


  reply	other threads:[~2007-08-13 18:08 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
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 [this message]
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=20070813180757.GZ23758@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).