All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <jejb@steeleye.com>
To: Christoph Hellwig <hch@lst.de>
Cc: g.liakhovetski@gmx.de, SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] merge scsiiom.c into tmscsim.c
Date: 09 Oct 2004 08:02:29 -0500	[thread overview]
Message-ID: <1097326958.2141.2.camel@mulgrave> (raw)
In-Reply-To: <20041009122946.GA19272@lst.de>

On Sat, 2004-10-09 at 07:29, Christoph Hellwig wrote:
> On Sun, Oct 03, 2004 at 03:47:14PM +0200, Christoph Hellwig wrote:
> > might be a good time to get rid of that clumsy include .c file into
> > another one thing.  (Also please bk rm scsiiom.c afterwards)
> 
> And here's a patch ontop that restores's Al's sparse fixes done in
> scsiiom.c (the old patch still applies and works without this one,
> but without it you get a few more sparse warnings):

I can't apply this patch without previously applying the tmscsim: remove
remaining INQUIRY sniffing.  In reply to that patch Guennadi said:

    So, I just wanted to let the so far submitted patches settle down a
    bit, at least hear some reaction to them, and then submit this one.
    But yours looks a bit better: I overlooked the possibility to do
    srb->pcmd->device, and added a dcb->sdev pointer to get to sdtr. So,
    be it yours.
    
Which I interpreted to mean wait a while before applying.

So, I can either apply both or neither.  Which is it to be?

James



  reply	other threads:[~2004-10-09 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-03 13:47 [PATCH] merge scsiiom.c into tmscsim.c Christoph Hellwig
2004-10-03 20:42 ` Guennadi Liakhovetski
2004-10-09 12:29 ` Christoph Hellwig
2004-10-09 13:02   ` James Bottomley [this message]
2004-10-09 19:18     ` Guennadi Liakhovetski
2007-06-17 15:09 ` Guennadi Liakhovetski
2007-06-17 16:25   ` Boaz Harrosh
2007-06-17 18:09     ` Guennadi Liakhovetski

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=1097326958.2141.2.camel@mulgrave \
    --to=jejb@steeleye.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.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 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.