From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
"dlemoal@kernel.org" <dlemoal@kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>
Subject: Re: [PATCH V2] nvmet: fix compilation errors
Date: Thu, 16 Jan 2025 01:16:41 +0000 [thread overview]
Message-ID: <5d1afcbe-95d6-4599-b9e9-5c97915446fb@nvidia.com> (raw)
In-Reply-To: <Z4g3z8GWgoCQd8Kh@kbusch-mbp>
On 1/15/25 14:33, Keith Busch wrote:
> On Wed, Jan 15, 2025 at 03:22:05PM -0700, Jens Axboe wrote:
>> What is this against? There's been no changes in the nvme tree since I
>> pulled it, and it doesn't apply here at all to my for-6.14/block branch.
> It looks like its against the merge result of the secure concatenation
> series, which as you know has been withdrawn. So this patch isn't
> necessary.
nvme tree branch nvme-6.14 with HEAD :-
commit 4a324970fabad503260973cd588609f3a26baab9 (tag:
nvme-6.14-2025-01-12, origin/nvme-6.14)
Author: Francis Pravin <francis.p@samsung.com>
Date: Fri Jan 10 05:21:37 2025 +0530
nvme-pci: use correct size to free the hmb buffer
is resulting in the compilation error, hence I send that patch.
-ck
next prev parent reply other threads:[~2025-01-16 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 22:17 [PATCH V2] nvmet: fix compilation errors Chaitanya Kulkarni
2025-01-15 22:22 ` Jens Axboe
2025-01-15 22:33 ` Keith Busch
2025-01-15 22:34 ` Jens Axboe
2025-01-16 1:16 ` Chaitanya Kulkarni [this message]
2025-01-16 1:56 ` Jens Axboe
2025-01-16 1:15 ` Chaitanya Kulkarni
2025-01-15 22:33 ` Jens Axboe
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=5d1afcbe-95d6-4599-b9e9-5c97915446fb@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@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