From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <kch@nvidia.com>, linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
dlemoal@kernel.org, bvanassche@acm.org
Subject: Re: [PATCH V2] nvmet: fix compilation errors
Date: Wed, 15 Jan 2025 15:22:05 -0700 [thread overview]
Message-ID: <6ca7f59b-f232-4bf0-984e-a4439e22b9ba@kernel.dk> (raw)
In-Reply-To: <20250115221703.62861-1-kch@nvidia.com>
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.
--
Jens Axboe
next prev parent reply other threads:[~2025-01-15 22:22 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 [this message]
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
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=6ca7f59b-f232-4bf0-984e-a4439e22b9ba@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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