From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scsi-disk: Inquiry with allocation length of CDB < 36
Date: Wed, 28 Oct 2009 12:31:49 +0100 [thread overview]
Message-ID: <fb8d4f70910280431u3a2dbb7bv4b9ce640467be04f@mail.gmail.com> (raw)
In-Reply-To: <fb8d4f70910271109r2b2fb673v57667ea54182e207@mail.gmail.com>
2009/10/27 Artyom Tarasenko <atar4qemu@googlemail.com>:
> 2009/10/27 Anthony Liguori <anthony@codemonkey.ws>:
>> Artyom Tarasenko wrote:
>>>
>>> According to SCSI-2 specification,
>>> http://ldkelley.com/SCSI2/SCSI2/SCSI2/SCSI2-08.html#8.2.5 ,
>>> "if the allocation length of the command descriptor block (CDB) is too
>>> small to transfer
>>> all of the parameters, the additional length shall not be adjusted to
>>> reflect the truncation."
>>> The 36 mandatory bytes of response are written to outbuf, and then
>>> only the length requested
>>> in CDB is transferred.
>>>
>>> Signed-off-by: Artyom Tarasenko <atar4qemu@gmail.com>
>>>
>>
>> This patch is whitespace damaged.
>
> Also the attached one? I tried to keep the original indentation: used
> tabs where the tabs originally were.
What is actually the indentation policy for patches? Should they be
conform with CODING_STYLE even if the original code isn't?
If they are conform the code may look badly indented with any tab
settings, including the ones from the original author.
If they keep author's indentation, the code still may look badly
indented with the CODING_STYLE tab settings.
Should patches for badly indented code explicitly require
indentation-only patches which shall be applied before?
prev parent reply other threads:[~2009-10-28 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 13:36 [Qemu-devel] [PATCH] scsi-disk: Inquiry with allocation length of CDB < 36 Artyom Tarasenko
2009-10-27 18:03 ` Anthony Liguori
2009-10-27 18:09 ` Artyom Tarasenko
2009-10-28 11:31 ` Artyom Tarasenko [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=fb8d4f70910280431u3a2dbb7bv4b9ce640467be04f@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).