From: Christoph Hellwig <hch@infradead.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, Kurt Garloff <kurt@garloff.de>
Subject: Re: [PATCH, 2.6] tmscsim - no internal command-queuing
Date: Thu, 19 Feb 2004 15:13:33 +0000 [thread overview]
Message-ID: <20040219151333.A24006@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0402032337230.3772-100000@poirot.grange>; from g.liakhovetski@gmx.de on Tue, Feb 03, 2004 at 11:41:43PM +0100
> Ouch. Whereas the rest are either rather intelligent things I didn't know
> about, or something I didn't want / dare to modify without a burning need,
> this is definitely just a plain simple bug - I did see it was a noop, and
> I did think at some point to preserve its consistency, until I forgot
> about it:-)
Kurt, do you have any opinion on those patches? I'd love to see them going
in for 2.6.4
next prev parent reply other threads:[~2004-02-19 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 23:23 [PATCH, 2.6] tmscsim - no internal command-queuing Guennadi Liakhovetski
2004-02-01 11:17 ` Christoph Hellwig
2004-02-01 15:41 ` James Bottomley
2004-02-03 22:41 ` Guennadi Liakhovetski
2004-02-19 15:13 ` Christoph Hellwig [this message]
2004-05-20 23:02 ` Kurt Garloff
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=20040219151333.A24006@infradead.org \
--to=hch@infradead.org \
--cc=g.liakhovetski@gmx.de \
--cc=kurt@garloff.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox