All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Jens Axboe <axboe@kernel.dk>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "kbusch@kernel.org" <kbusch@kernel.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:15:21 +0000	[thread overview]
Message-ID: <a4299529-15ca-4187-8a7c-d1c43fee92db@nvidia.com> (raw)
In-Reply-To: <6ca7f59b-f232-4bf0-984e-a4439e22b9ba@kernel.dk>

On 1/15/25 14:22, 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 is against nvme tree branch nvme-6.14 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

-ck



  parent reply	other threads:[~2025-01-16  1:15 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
2025-01-16  1:56       ` Jens Axboe
2025-01-16  1:15   ` Chaitanya Kulkarni [this message]
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=a4299529-15ca-4187-8a7c-d1c43fee92db@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 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.