From: Johannes Berg <johannes@sipsolutions.net>
To: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>,
Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rfkill: uapi: fix RFKILL_IOCTL_MAX_SIZE ioctl request definition
Date: Fri, 06 May 2022 19:21:11 +0200 [thread overview]
Message-ID: <c66b3c0ba5d6076b00718f6df53f37ec8b099a04.camel@sipsolutions.net> (raw)
In-Reply-To: <20220506171534.99509-1-glebfm@altlinux.org>
On Fri, 2022-05-06 at 17:15 +0000, Gleb Fotengauer-Malinovskiy wrote:
> Fixes: 54f586a91532 ("rfkill: make new event layout opt-in")
> ---
> include/uapi/linux/rfkill.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/rfkill.h b/include/uapi/linux/rfkill.h
> index 283c5a7b3f2c..db6c8588c1d0 100644
> --- a/include/uapi/linux/rfkill.h
> +++ b/include/uapi/linux/rfkill.h
> @@ -184,7 +184,7 @@ struct rfkill_event_ext {
> #define RFKILL_IOC_NOINPUT 1
> #define RFKILL_IOCTL_NOINPUT _IO(RFKILL_IOC_MAGIC, RFKILL_IOC_NOINPUT)
> #define RFKILL_IOC_MAX_SIZE 2
> -#define RFKILL_IOCTL_MAX_SIZE _IOW(RFKILL_IOC_MAGIC, RFKILL_IOC_EXT_SIZE, __u32)
> +#define RFKILL_IOCTL_MAX_SIZE _IOW(RFKILL_IOC_MAGIC, RFKILL_IOC_MAX_SIZE, __u32)
>
Oops. But I still need your Signed-off-by (see the documentation), and a
commit message would be nice :)
johannes
next prev parent reply other threads:[~2022-05-06 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 17:15 [PATCH] rfkill: uapi: fix RFKILL_IOCTL_MAX_SIZE ioctl request definition Gleb Fotengauer-Malinovskiy
2022-05-06 17:21 ` Johannes Berg [this message]
2022-05-06 17:24 ` [PATCH v2] " Gleb Fotengauer-Malinovskiy
2022-05-07 7:05 ` Greg KH
2022-05-07 8:45 ` Dmitry V. Levin
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=c66b3c0ba5d6076b00718f6df53f37ec8b099a04.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=glebfm@altlinux.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 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).