From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Jemmy Wong <jemmywong512@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tools/nolibc/types.h: fix mismatched parenthesis in minor()
Date: Wed, 9 Apr 2025 21:19:40 +0200 [thread overview]
Message-ID: <c232e7ec-9e39-45e8-9d90-c8e4d16c77a4@t-8ch.de> (raw)
In-Reply-To: <20250409191436.75658-1-jemmywong512@gmail.com>
Hi Jemmy,
On 2025-04-10 03:14:36+0800, Jemmy Wong wrote:
> Fix an imbalance where opening parentheses exceed closing ones.
Thanks! The patch looks good and I will pick it up soonish.
One note: When sending new revisions of patches, please always include a
changelog of all differences in the new revision.
I can also recommend the b4 tool for taking care of many workflow tasks.
https://b4.docs.kernel.org/en/latest/
> Signed-off-by: Jemmy Wong <Jemmywong512@gmail.com>
> ---
> tools/include/nolibc/types.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/include/nolibc/types.h b/tools/include/nolibc/types.h
> index b26a5d0c417c..32d0929c633b 100644
> --- a/tools/include/nolibc/types.h
> +++ b/tools/include/nolibc/types.h
> @@ -201,7 +201,7 @@ struct stat {
> /* WARNING, it only deals with the 4096 first majors and 256 first minors */
> #define makedev(major, minor) ((dev_t)((((major) & 0xfff) << 8) | ((minor) & 0xff)))
> #define major(dev) ((unsigned int)(((dev) >> 8) & 0xfff))
> -#define minor(dev) ((unsigned int)(((dev) & 0xff))
> +#define minor(dev) ((unsigned int)((dev) & 0xff))
>
> #ifndef offsetof
> #define offsetof(TYPE, FIELD) ((size_t) &((TYPE *)0)->FIELD)
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-09 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 19:14 Jemmy Wong
2025-04-09 19:19 ` Thomas Weißschuh [this message]
2025-04-09 19:19 ` Willy Tarreau
2025-04-10 20:08 ` Thomas Weißschuh
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=c232e7ec-9e39-45e8-9d90-c8e4d16c77a4@t-8ch.de \
--to=linux@weissschuh.net \
--cc=jemmywong512@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®