public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Lei Rao <lei.rao@intel.com>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	hang.yuan@intel.com
Subject: Re: [PATCH] nvme: clear the prp2 field of the nvme command.
Date: Tue, 29 Nov 2022 14:38:56 +0100	[thread overview]
Message-ID: <20221129133856.GA13668@lst.de> (raw)
In-Reply-To: <20221129094811.893586-1-lei.rao@intel.com>

Thanks,

I've applied the patch with a slightly update commit message to the
nvme-6.1 tree.

  reply	other threads:[~2022-11-29 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  9:48 [PATCH] nvme: clear the prp2 field of the nvme command Lei Rao
2022-11-29 13:38 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-29  1:47 Lei Rao
2022-11-29  4:16 ` Chaitanya Kulkarni
2022-11-29  4:50   ` Rao, Lei
2022-11-29  8:43     ` hch
2022-11-29  8:41 ` Christoph Hellwig

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=20221129133856.GA13668@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=hang.yuan@intel.com \
    --cc=kbusch@kernel.org \
    --cc=lei.rao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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