From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Vogt <michael.vogt@gmail.com>, qemu-devel@nongnu.org
Cc: Michael Vogt <mvogt@redhat.com>, qemu-trivial@nongnu.org
Subject: Re: [PATCH] linux-user: Add ioctl for BLKBSZSET
Date: Wed, 29 May 2024 08:20:16 -0700 [thread overview]
Message-ID: <0ded3230-3b56-45ed-afe7-a4bd7d99dc76@linaro.org> (raw)
In-Reply-To: <CAPOxN2FyxFp+BJzgFa=EkxDkrctBg5TZWWW1x7r0tKONLHJ7Jg@mail.gmail.com>
On 5/29/24 00:56, Michael Vogt wrote:
> Friendly ping
>
> I tested the patch as part of cross architecture build (using qemu-user) with
> bootc-image-builder in https://github.com/osbuild/bootc-image-builder/pull/342
> <https://github.com/osbuild/bootc-image-builder/pull/342> (not sure that is relevant, but
> I wanted to mention that it is working for my test-case).
>
> On Tue, Apr 23, 2024 at 5:25 PM Michael Vogt <michael.vogt@gmail.com
> <mailto:michael.vogt@gmail.com>> wrote:
>
> Tiny patch to add the ioctl wrapper definition for BLKBSZSET.
>
> Signed-off-by: Michael Vogt <mvogt@redhat.com <mailto:mvogt@redhat.com>>
> ---
> linux-user/ioctls.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/linux-user/ioctls.h b/linux-user/ioctls.h
> index d508d0c04a..3b41128fd7 100644
> --- a/linux-user/ioctls.h
> +++ b/linux-user/ioctls.h
> @@ -102,6 +102,7 @@
> IOCTL(BLKRAGET, IOC_R, MK_PTR(TYPE_LONG))
> IOCTL(BLKSSZGET, IOC_R, MK_PTR(TYPE_INT))
> IOCTL(BLKBSZGET, IOC_R, MK_PTR(TYPE_INT))
> + IOCTL(BLKBSZSET, IOC_W, MK_PTR(TYPE_INT))
> IOCTL_SPECIAL(BLKPG, IOC_W, do_ioctl_blkpg,
> MK_PTR(MK_STRUCT(STRUCT_blkpg_ioctl_arg)))
>
> --
> 2.43.0
>
Queued, thanks.
r~
prev parent reply other threads:[~2024-05-29 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 15:24 [PATCH] linux-user: Add ioctl for BLKBSZSET Michael Vogt
2024-05-29 7:56 ` Michael Vogt
2024-05-29 15:20 ` Richard Henderson [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=0ded3230-3b56-45ed-afe7-a4bd7d99dc76@linaro.org \
--to=richard.henderson@linaro.org \
--cc=michael.vogt@gmail.com \
--cc=mvogt@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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;
as well as URLs for NNTP newsgroup(s).