From: Steffen Maier <maier@linux.vnet.ibm.com>
To: Kyle Fortin <kyle.fortin@oracle.com>,
Randy Dunlap <rdunlap@infradead.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>
Subject: Re: [PATCH] scsi: logging_level: update bits description
Date: Wed, 11 Oct 2017 15:18:27 +0200 [thread overview]
Message-ID: <ccfbbfed-b1e4-2db8-12a4-76d083f0a474@linux.vnet.ibm.com> (raw)
In-Reply-To: <216D3DB1-C329-4B75-8210-822FF889C344@oracle.com>
On 10/10/2017 09:32 PM, Kyle Fortin wrote:
> On Oct 10, 2017, at 3:05 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Update the description of 'scsi_logging_level' from 8 4-bit nibbles
>> to the (pre-git) reality of 10 3-bit 'nibbles'.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> ---
>> drivers/scsi/scsi_logging.h | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> --- lnx-414-rc3.orig/drivers/scsi/scsi_logging.h
>> +++ lnx-414-rc3/drivers/scsi/scsi_logging.h
>> @@ -3,10 +3,10 @@
>>
>>
>> /*
>> - * This defines the scsi logging feature. It is a means by which the user
>> - * can select how much information they get about various goings on, and it
>> - * can be really useful for fault tracing. The logging word is divided into
nit pick: Why reflow and thus "change" these 3 lines even though the
content is the same?
>> - * 8 nibbles, each of which describes a loglevel. The division of things is
>> + * This defines the scsi logging feature. It is a means by which the user can
>> + * select how much information they get about various goings on, and it can be
>> + * really useful for fault tracing. The logging word is divided into 10 3-bit
>> + * 'nibbles', each of which describes a loglevel. The division of things is
>
> I think ‘bitfields' is more appropriate than ‘nibbles’ (a 4-bit construct in compute).
+1
>> * somewhat arbitrary, and the division of the word could be changed if it
>> * were really needed for any reason. The numbers below are the only place
>> * where these are specified. For a first go-around, 3 bits is more than
>
> Reviewed-by: Kyle Fortin <kyle.fortin@oracle.com>
Reviewed-by: Steffen Maier <maier@linux.vnet.ibm.com>
--
Mit freundlichen Grüßen / Kind regards
Steffen Maier
Linux on z Systems Development
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2017-10-11 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 19:05 [PATCH] scsi: logging_level: update bits description Randy Dunlap
2017-10-10 19:32 ` Kyle Fortin
2017-10-11 13:18 ` Steffen Maier [this message]
2017-10-11 16:15 ` Randy Dunlap
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=ccfbbfed-b1e4-2db8-12a4-76d083f0a474@linux.vnet.ibm.com \
--to=maier@linux.vnet.ibm.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kyle.fortin@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@infradead.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).