From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Alessio Balsini <balsini@android.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
kernel-team@android.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fuse: fix integer type usage in uapi header
Date: Sat, 19 Mar 2022 07:40:18 +0100 [thread overview]
Message-ID: <YjV60vyVkMXrkla/@kroah.com> (raw)
In-Reply-To: <20220318171405.2728855-1-cmllamas@google.com>
On Fri, Mar 18, 2022 at 05:14:05PM +0000, Carlos Llamas wrote:
> Kernel uapi headers are supposed to use __[us]{8,16,32,64} defined by
> <linux/types.h> instead of 'uint32_t' and similar. This patch changes
> all the definitions in this header to use the correct type. Previous
> discussion of this topic can be found here:
>
> https://lkml.org/lkml/2019/6/5/18
>
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> ---
> include/uapi/linux/fuse.h | 509 +++++++++++++++++++-------------------
> 1 file changed, 253 insertions(+), 256 deletions(-)
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2022-03-19 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 17:14 [PATCH] fuse: fix integer type usage in uapi header Carlos Llamas
2022-03-18 17:23 ` Masahiro Yamada
2022-03-18 19:24 ` Miklos Szeredi
2022-03-19 6:40 ` Greg Kroah-Hartman
2022-03-21 2:07 ` Carlos Llamas
2022-03-21 8:40 ` Miklos Szeredi
2022-03-21 8:50 ` Greg Kroah-Hartman
2022-03-21 9:36 ` Miklos Szeredi
2022-03-21 10:01 ` Greg Kroah-Hartman
2022-03-21 11:25 ` Miklos Szeredi
2022-03-21 12:28 ` Greg Kroah-Hartman
2022-03-19 6:40 ` Greg Kroah-Hartman [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=YjV60vyVkMXrkla/@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=balsini@android.com \
--cc=cmllamas@google.com \
--cc=kernel-team@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miklos@szeredi.hu \
/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.