All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Doug Ledford <dledford@redhat.com>
Cc: Martin Peschke3 <MPESCHKE@de.ibm.com>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-scsi mailing list <linux-scsi@vger.kernel.org>,
	andmike@us.ibm.com, garloff@suse.de
Subject: Re: [PATCH] 2.4.25-pre8: loss of SCSI I/O initiative
Date: Tue, 3 Feb 2004 10:07:38 +0100	[thread overview]
Message-ID: <20040203090738.GX11683@suse.de> (raw)
In-Reply-To: <1075747729.3248.17.camel@compaq.xsintricity.com>

On Mon, Feb 02 2004, Doug Ledford wrote:
> On Mon, 2004-02-02 at 12:42, Martin Peschke3 wrote:
> > 
> > 
> > Marcelo, Doug,
> > 
> > here is another patch, which corrects some 'loss of initiative' problems.
> 
> Hi Martin.  Both of the patches you posted touch areas of code that are
> also touched by some of the patches I'm merging for the everything
> tree.  So, Marcelo, whether or not to take these depends partially on
> your decision as to what to do with the other scsi patches we've got
> here and that SuSE has.  In particular, it's possible that the mlqueue
> patch that I haven't got in my 2.4-everything tree yet may very well
> obsolete the need for one of these, and another patch in our tree may
> obsolete the need for the other.  I'm not sure yet.  Anyway, just wanted
> to let you know that if you are considering the bigger set of SCSI
> patches (and yes, I'm sure you want to see them before you would ever
> say yes, I'm just not sure if you've already decided that your answer is
> "no") then both of these patches from Martin would have to be merged
> with the final product and might not be necessary in the end, or if they
> are necessary I'm sure they'll have a slightly different form.

The patches Martin sent could be merged before any pending bigger
merges - they are pretty straight forward. I'd rather not put smaller
changes like that into bigger trees and merge all of those at one time
if only because it doesn't exactly help bug finding...

So in my opinion, they should just go straight to Marcelo.

-- 
Jens Axboe


  reply	other threads:[~2004-02-03  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 17:42 [PATCH] 2.4.25-pre8: loss of SCSI I/O initiative Martin Peschke3
2004-02-02 18:48 ` Doug Ledford
2004-02-03  9:07   ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02 20:42 Martin Peschke3

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=20040203090738.GX11683@suse.de \
    --to=axboe@suse.de \
    --cc=MPESCHKE@de.ibm.com \
    --cc=andmike@us.ibm.com \
    --cc=dledford@redhat.com \
    --cc=garloff@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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.