qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gollu Appalanaidu <anaidu.gollu@samsung.com>
To: Klaus Jensen <its@irrelevant.dk>
Cc: fam@euphon.net, kwolf@redhat.com, qemu-block@nongnu.org,
	qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	stefanha@redhat.com, kbusch@kernel.org, mreitz@redhat.com,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] hw/block/nvme: align with existing style
Date: Fri, 16 Apr 2021 00:00:08 +0530	[thread overview]
Message-ID: <20210415183008.GA8777@2030045822> (raw)
In-Reply-To: <YHh1evjljdZesw5I@apples.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

On Thu, Apr 15, 2021 at 07:18:50PM +0200, Klaus Jensen wrote:
>On Apr 15 15:13, Philippe Mathieu-Daudé wrote:
>>On 4/15/21 2:00 PM, Gollu Appalanaidu wrote:
>>>Make uniform hexadecimal numbers format.
>>>
>>>Signed-off-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
>>>---
>>>-v2: Address review comments (Klaus)
>>>use lower case hexa format for the code and in comments
>>>use the same format as used in Spec. ("FFFFFFFFh")
>>
>>^ This comment is relevant to the commit message.
>>
>>Also it would be nice if the subsystem could describe somewhere
>>what is its style. Not sure where... The file header is probably
>>the simplest place.
>>
>>Something like:
>>
>>"While QEMU coding style prefers lowercase hexadecimal in constants,
>>the NVMe subsystem use the format from the NVMe specifications in
>>the comments: no '0x' prefix, uppercase, 'h' hexadecimal suffix."
>>
>
>+1 for that suggestion.
>

Sure, will add it and send v3.

>>> hw/block/nvme-ns.c   |  2 +-
>>> hw/block/nvme.c      | 40 ++++++++++++++++++++--------------------
>>> include/block/nvme.h | 10 +++++-----
>>> 3 files changed, 26 insertions(+), 26 deletions(-)
>>
>>



[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2021-04-16  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210415120417epcas5p31ddb152cbe94fa5bebe386de5e33f69e@epcas5p3.samsung.com>
2021-04-15 12:00 ` [PATCH v2] hw/block/nvme: align with existing style Gollu Appalanaidu
2021-04-15 13:13   ` Philippe Mathieu-Daudé
2021-04-15 17:18     ` Klaus Jensen
2021-04-15 18:30       ` Gollu Appalanaidu [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=20210415183008.GA8777@2030045822 \
    --to=anaidu.gollu@samsung.com \
    --cc=armbru@redhat.com \
    --cc=fam@euphon.net \
    --cc=its@irrelevant.dk \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).