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] fix mismatched parentheses
Date: Wed, 9 Apr 2025 20:30:14 +0200 [thread overview]
Message-ID: <bb44ee43-b08f-4a4a-bdde-dda785756680@t-8ch.de> (raw)
In-Reply-To: <20250409181934.5589-1-jemmywong512@gmail.com>
Hi Jemmy,
good catch and thanks for your patch!
There are some small formal issues with it, though.
Could you fix those and send a v2?
The patch subject should start with "tools/nolibc: ", and could be a bit
more specific: "fix mismatched parenthesis in minor()"
(more below)
On 2025-04-10 02:19:34+0800, Jemmy Wong wrote:
> Corrects an imbalance where opening parentheses exceed closing ones.
Use imperative language: "Correct an ..."
As this is a bugfix, a Fixes tag would be great.
In this case:
Fixes: eba6d00d38e7 ("tools/nolibc/types: move makedev to types.h and make it a macro")
> 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..b57e054cca82 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)
Thomas
next prev parent reply other threads:[~2025-04-09 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 18:19 Jemmy Wong
2025-04-09 18:30 ` Thomas Weißschuh [this message]
2025-04-09 19:07 ` Jemmy Wong
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=bb44ee43-b08f-4a4a-bdde-dda785756680@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®