From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH blktests 3/3] src: add nvme-passthru-admin-uring to .gitignore
Date: Thu, 26 Feb 2026 05:39:22 +0000 [thread overview]
Message-ID: <7f2329c1-b3bf-4bf5-bbce-1abe28bc16a5@nvidia.com> (raw)
In-Reply-To: <20260223074110.144758-4-shinichiro.kawasaki@wdc.com>
On 2/22/26 23:41, Shin'ichiro Kawasaki wrote:
> Commit a94b77010d56 ("nvme/067: test io_uring pass through for NVMe
> admin queue") introduced a new program nvme-passthru-admin-uring under
> /src directory, but omitted it from .gitignore. Add it to .gitignore.
>
> Fixes: a94b77010d56 ("nvme/067: test io_uring pass through for NVMe admin queue")
> Signed-off-by: Shin'ichiro Kawasaki<shinichiro.kawasaki@wdc.com>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2026-02-26 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 7:41 [PATCH blktests 0/3] misc fixes Shin'ichiro Kawasaki
2026-02-23 7:41 ` [PATCH blktests 1/3] common/nvme: do not call 'nvme id-ns' to non-nvme devices Shin'ichiro Kawasaki
2026-02-26 5:38 ` Chaitanya Kulkarni
2026-02-23 7:41 ` [PATCH blktests 2/3] check: increment bash requirement version from 4.2 to 4.3 Shin'ichiro Kawasaki
2026-02-26 5:39 ` Chaitanya Kulkarni
2026-02-23 7:41 ` [PATCH blktests 3/3] src: add nvme-passthru-admin-uring to .gitignore Shin'ichiro Kawasaki
2026-02-26 5:39 ` Chaitanya Kulkarni [this message]
2026-03-02 0:32 ` [PATCH blktests 0/3] misc fixes Shinichiro Kawasaki
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=7f2329c1-b3bf-4bf5-bbce-1abe28bc16a5@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
/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