From: Jens Axboe <axboe@kernel.dk>
To: Uday Shankar <ushankar@purestorage.com>,
Ming Lei <ming.lei@redhat.com>, Shuah Khan <shuah@kernel.org>
Cc: linux-block@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] selftests: ublk: more misc fixes
Date: Mon, 5 May 2025 16:44:19 -0600 [thread overview]
Message-ID: <3a6050b3-03f6-4c22-a2c3-33ab6a453376@kernel.dk> (raw)
In-Reply-To: <aBkg0LW5YO6Osdnw@dev-ushankar.dev.purestorage.com>
On 5/5/25 2:34 PM, Uday Shankar wrote:
> On Mon, May 05, 2025 at 02:31:40PM -0600, Uday Shankar wrote:
>> Hi Jens,
>>
>> Can you take a look at Ming's comment on the first patch and merge the
>> set if things look good? I can rebase/repost it as needed.
>
> Bleh, sorry, I meant to send this as a reply to v2:
>
> https://lore.kernel.org/linux-block/20250429-ublk_selftests-v2-0-e970b6d9e4f4@purestorage.com/
Let's give Ming a chance to review v2, then I can get it queued up.
--
Jens Axboe
next prev parent reply other threads:[~2025-05-05 22:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 23:10 [PATCH 0/3] selftests: ublk: more misc fixes Uday Shankar
2025-04-28 23:10 ` [PATCH 1/3] selftests: ublk: kublk: build with -Werror iff CONFIG_WERROR=y Uday Shankar
2025-04-29 1:11 ` Ming Lei
2025-04-29 22:46 ` Uday Shankar
2025-04-28 23:10 ` [PATCH 2/3] selftests: ublk: make test_generic_06 silent on success Uday Shankar
2025-04-29 1:12 ` Ming Lei
2025-04-28 23:10 ` [PATCH 3/3] selftests: ublk: kublk: fix include path Uday Shankar
2025-04-29 1:14 ` Caleb Sander Mateos
2025-04-29 22:43 ` Uday Shankar
2025-04-29 1:22 ` Ming Lei
2025-05-05 20:31 ` [PATCH 0/3] selftests: ublk: more misc fixes Uday Shankar
2025-05-05 20:34 ` Uday Shankar
2025-05-05 22:44 ` Jens Axboe [this message]
2025-05-05 22:53 ` Uday Shankar
2025-05-05 22:55 ` 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=3a6050b3-03f6-4c22-a2c3-33ab6a453376@kernel.dk \
--to=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 \
--cc=ushankar@purestorage.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