All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Engel, Amit" <Amit.Engel@Dell.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: RE: [PATCH] nvmet: fix per feat data len for get_feature
Date: Thu, 12 Dec 2019 09:40:38 +0000	[thread overview]
Message-ID: <MWHPR19MB1487CC35002824911B4C8CA8EE550@MWHPR19MB1487.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20191212093927.GA3388@lst.de>

Sure, thank you

-----Original Message-----
From: Christoph Hellwig <hch@lst.de> 
Sent: Thursday, December 12, 2019 11:39 AM
To: Engel, Amit
Cc: Christoph Hellwig; Chaitanya Kulkarni; linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: fix per feat data len for get_feature


[EXTERNAL EMAIL] 

On Thu, Dec 12, 2019 at 09:14:15AM +0000, Engel, Amit wrote:
> Chaitanya, do you fix the double author line? Do you want me to do it?

We usually handle such minor nitpicks when applying the patch, no need to resend.

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      reply	other threads:[~2019-12-12  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  7:22 [PATCH] nvmet: fix per feat data len for get_feature Chaitanya Kulkarni
2019-12-11  5:09 ` Chaitanya Kulkarni
2019-12-12  9:07 ` Christoph Hellwig
2019-12-12  9:14   ` Engel, Amit
2019-12-12  9:39     ` Christoph Hellwig
2019-12-12  9:40       ` Engel, Amit [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=MWHPR19MB1487CC35002824911B4C8CA8EE550@MWHPR19MB1487.namprd19.prod.outlook.com \
    --to=amit.engel@dell.com \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.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 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.