From: Ming Lei <ming.lei@redhat.com>
To: Alexander Atanasov <alex@zazolabs.com>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH v2 4/4] selftests: ublk: cleanup kublk.h
Date: Sat, 28 Feb 2026 18:07:47 +0800 [thread overview]
Message-ID: <aaK-c4WbTlpewltn@fedora> (raw)
In-Reply-To: <20260227145756.3877069-5-alex@zazolabs.com>
On Fri, Feb 27, 2026 at 02:57:56PM +0000, Alexander Atanasov wrote:
> Arguments are handled via flags so
> remove unused no_auto_part_scan bitfield.
>
> Signed-off-by: Alexander Atanasov <alex@zazolabs.com>
> ---
> tools/testing/selftests/ublk/kublk.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/testing/selftests/ublk/kublk.h b/tools/testing/selftests/ublk/kublk.h
> index 1faeccaaecae..3379e49449b4 100644
> --- a/tools/testing/selftests/ublk/kublk.h
> +++ b/tools/testing/selftests/ublk/kublk.h
> @@ -79,7 +79,6 @@ struct dev_ctx {
> unsigned int per_io_tasks:1;
> unsigned int no_ublk_fixed_fd:1;
> unsigned int safe_stop:1;
> - unsigned int no_auto_part_scan:1;
> __u32 integrity_flags;
> __u8 metadata_size;
> __u8 pi_offset;
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks,
Ming
prev parent reply other threads:[~2026-02-28 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:57 [PATCH v2 0/4] ublk: rework partition handling Alexander Atanasov
2026-02-27 14:57 ` [PATCH v2 1/4] ublk: cleanup partition flags handling and introduce UBLK_F_NO_PARTITONS Alexander Atanasov
2026-02-27 18:29 ` Caleb Sander Mateos
2026-02-28 2:06 ` Ming Lei
2026-02-28 5:30 ` Alexander Atanasov
2026-02-28 7:19 ` Ming Lei
2026-02-27 14:57 ` [PATCH v2 2/4] selftests: ublk: rework partitions tests for new flags Alexander Atanasov
2026-02-28 10:06 ` Ming Lei
2026-02-27 14:57 ` [PATCH v2 3/4] ublk: document partition flags, kublk and update external links Alexander Atanasov
2026-02-28 10:07 ` Ming Lei
2026-02-27 14:57 ` [PATCH v2 4/4] selftests: ublk: cleanup kublk.h Alexander Atanasov
2026-02-28 10:07 ` Ming Lei [this message]
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=aaK-c4WbTlpewltn@fedora \
--to=ming.lei@redhat.com \
--cc=alex@zazolabs.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.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 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.