From: Uday Shankar <ushankar@purestorage.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <ming.lei@redhat.com>, Shuah Khan <shuah@kernel.org>,
linux-block@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ublk: fixes for selftests
Date: Wed, 2 Apr 2025 13:34:20 -0600 [thread overview]
Message-ID: <Z+2RPI1GC9NoE/w4@dev-ushankar.dev.purestorage.com> (raw)
In-Reply-To: <174359956539.20480.17105268115889494986.b4-ty@kernel.dk>
On Wed, Apr 02, 2025 at 07:12:45AM -0600, Jens Axboe wrote:
>
> On Tue, 01 Apr 2025 14:49:07 -0600, Uday Shankar wrote:
> > Fix a couple of issues I saw when developing selftests for ublk. These
> > patches are split out from the following series:
> >
> > https://lore.kernel.org/linux-block/20250325-ublk_timeout-v1-0-262f0121a7bd@purestorage.com/T/#t
> >
> >
>
> Applied, thanks!
>
> [1/2] selftests: ublk: kublk: use ioctl-encoded opcodes
> (no commit info)
> [2/2] selftests: ublk: kublk: fix an error log line
> (no commit info)
Jens, MAINTAINERS parsing didn't add you to this email - I had to do it
manually. Do we need to add you somewhere so you get a copy of all ublk
patches (since you maintain its tree)?
next prev parent reply other threads:[~2025-04-02 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 20:49 [PATCH 0/2] ublk: fixes for selftests Uday Shankar
2025-04-01 20:49 ` [PATCH 1/2] selftests: ublk: kublk: use ioctl-encoded opcodes Uday Shankar
2025-04-01 20:49 ` [PATCH 2/2] selftests: ublk: kublk: fix an error log line Uday Shankar
2025-04-02 13:12 ` [PATCH 0/2] ublk: fixes for selftests Jens Axboe
2025-04-02 19:34 ` Uday Shankar [this message]
2025-04-02 19:42 ` 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=Z+2RPI1GC9NoE/w4@dev-ushankar.dev.purestorage.com \
--to=ushankar@purestorage.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=shuah@kernel.org \
/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