From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <nks@flawful.org>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me,
niklas.cassel@wdc.com, joshi.k@samsung.com, javier@javigon.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] nvme: disallow passthru cmd from targeting a nsid != nsid of the block dev
Date: Sat, 3 Apr 2021 10:15:56 +0200 [thread overview]
Message-ID: <20210403081556.GA26879@lst.de> (raw)
In-Reply-To: <20210402201808.31979-1-nks@flawful.org>
So it turns out that while git-am complained it did apply the patch
just fine and it didn't look whitespace mangled. No idea what went
on there, but the patch is in nvme-5.13 now.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-04-03 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 20:18 [PATCH v3] nvme: disallow passthru cmd from targeting a nsid != nsid of the block dev Niklas Cassel
2021-04-03 8:15 ` Christoph Hellwig [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=20210403081556.GA26879@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=javier@javigon.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=niklas.cassel@wdc.com \
--cc=nks@flawful.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