From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alexander Bezzubikov <zuban32s@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] ATAPI-SCSI bridge GSoC project
Date: Mon, 20 Jul 2015 12:03:04 +0100 [thread overview]
Message-ID: <20150720110304.GC12675@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1437245366-20156-1-git-send-email-abezzubikov@ispras.ru>
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
On Sat, Jul 18, 2015 at 09:49:26PM +0300, Alexander Bezzubikov wrote:
> atapi: ATAPI-SCSI bridge device created
> private SCSI bus added to bridge
> ATAPI inquiry command can use a bridge
Multiple items is a clue that this patch should be split up into patches
with smaller logical changes.
That will also allow you to write commit descriptions that give the
rationale for the changes.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-07-20 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 18:49 [Qemu-devel] [RFC] ATAPI-SCSI bridge GSoC project Alexander Bezzubikov
2015-07-20 6:59 ` Thomas Huth
2015-07-20 11:03 ` Stefan Hajnoczi [this message]
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=20150720110304.GC12675@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=zuban32s@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).