From: Hannes Reinecke <hare@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org, nab@linux-iscsi.org
Subject: Re: [Qemu-devel] Re: [PATCH 10/16] scsi: Use 'SCSIRequest' directly
Date: Thu, 18 Nov 2010 17:33:38 +0100 [thread overview]
Message-ID: <4CE55562.7000600@suse.de> (raw)
In-Reply-To: <4CE55177.1020602@redhat.com>
On 11/18/2010 05:16 PM, Gerd Hoffmann wrote:
> On 11/18/10 15:47, Hannes Reinecke wrote:
>>
>> Rather than to access a SCSIRequest via an abstract 'tag' we can
>> as well use it directly and save us the lookup.
>
> Hmm. Looks like a few more request handling changes than a pure
> s/tag/req/ + zap lookups sneaked into that patch. There are new get_req
> and put_req callbacks for example. At minimum these changes must be
> documented in the commit message. Even better splitted into separate
> patches.
>
Not sure if it makes sense to split it up into several patches;
we need the ->get_req()/->put_req() callbacks to get the request in
the first place. And only then can we modify the other callbacks.
However, splitting them off into two patchsets would render the
first pretty much pointless.
But sure, I can do a better description.
Just tell me which direction you prefer.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2010-11-18 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 14:47 [Qemu-devel] [PATCH 10/16] scsi: Use 'SCSIRequest' directly Hannes Reinecke
2010-11-18 16:16 ` [Qemu-devel] " Gerd Hoffmann
2010-11-18 16:33 ` Hannes Reinecke [this message]
2010-11-19 8:02 ` Gerd Hoffmann
2010-11-19 18:27 ` [Qemu-devel] " Christoph Hellwig
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=4CE55562.7000600@suse.de \
--to=hare@suse.de \
--cc=kraxel@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).