All of lore.kernel.org
 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, mreitz@redhat.com, stefanha@redhat.com,
	kbusch@kernel.org
Subject: Re: [PATCH] hw/nvme/ctrl: fix functions style
Date: Mon, 24 May 2021 18:03:56 +0530	[thread overview]
Message-ID: <20210524123355.GA12134@2030045822> (raw)
In-Reply-To: <YKddr8UDZhPzK0Yr@apples.localdomain>

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

On Fri, May 21, 2021 at 09:13:51AM +0200, Klaus Jensen wrote:
>On May 21 11:38, Gollu Appalanaidu wrote:
>>Identify command related functions style fix.
>>
>>Signed-off-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
>>---
>>hw/nvme/ctrl.c | 6 +++---
>>1 file changed, 3 insertions(+), 3 deletions(-)
>>
>>diff --git a/hw/nvme/ctrl.c b/hw/nvme/ctrl.c
>>index 0bcaf7192f..40a7efcea9 100644
>>--- a/hw/nvme/ctrl.c
>>+++ b/hw/nvme/ctrl.c
>>@@ -4291,7 +4291,7 @@ static uint16_t nvme_identify_ns_attached_list(NvmeCtrl *n, NvmeRequest *req)
>>}
>>
>>static uint16_t nvme_identify_ns_csi(NvmeCtrl *n, NvmeRequest *req,
>>-        bool active)
>>+                                     bool active)
>>{
>>    NvmeNamespace *ns;
>>    NvmeIdentify *c = (NvmeIdentify *)&req->cmd;
>>@@ -4326,7 +4326,7 @@ static uint16_t nvme_identify_ns_csi(NvmeCtrl *n, NvmeRequest *req,
>>}
>>
>>static uint16_t nvme_identify_nslist(NvmeCtrl *n, NvmeRequest *req,
>>-        bool active)
>>+                                     bool active)
>>{
>>    NvmeNamespace *ns;
>>    NvmeIdentify *c = (NvmeIdentify *)&req->cmd;
>>@@ -4373,7 +4373,7 @@ static uint16_t nvme_identify_nslist(NvmeCtrl *n, NvmeRequest *req,
>>}
>>
>>static uint16_t nvme_identify_nslist_csi(NvmeCtrl *n, NvmeRequest *req,
>>-        bool active)
>>+                                         bool active)
>>{
>>    NvmeNamespace *ns;
>>    NvmeIdentify *c = (NvmeIdentify *)&req->cmd;
>>-- 
>>2.17.1
>>
>>
>
>Thanks, applied to nvme-next.
>
>Please just use 'hw/nvme:' in the commit title, we don't need to 
>specify the sub-subsystem ;)

Sure Klaus, Thanks :)


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



      reply	other threads:[~2021-05-25  3:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210521061352epcas5p145b3a19453f7ff9d625bb9ae447b649c@epcas5p1.samsung.com>
2021-05-21  6:08 ` [PATCH] hw/nvme/ctrl: fix functions style Gollu Appalanaidu
2021-05-21  7:13   ` Klaus Jensen
2021-05-24 12:33     ` 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=20210524123355.GA12134@2030045822 \
    --to=anaidu.gollu@samsung.com \
    --cc=fam@euphon.net \
    --cc=its@irrelevant.dk \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.