From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [PATCH 2/3] kobject: Improve a size determination in kobject_uevent_env()
Date: Tue, 19 Dec 2023 16:40:04 +0100 [thread overview]
Message-ID: <2023121946-immovable-striving-e2c7@gregkh> (raw)
In-Reply-To: <f007f92c-a355-4bb9-a715-aa42ee6c647b@web.de>
On Tue, Dec 19, 2023 at 04:34:19PM +0100, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Tue, 19 Dec 2023 16:00:22 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a bit safer according to the Linux coding style convention.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
Sorry, but for obvious reasons, I'm still not taking patches from you.
best of luck,
greg k-h
next prev parent reply other threads:[~2023-12-19 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 15:30 [cocci] [PATCH 0/3] kobject: Adjustments for kobject_uevent_env() Markus Elfring
2023-12-19 15:30 ` Markus Elfring
2023-12-19 15:32 ` [cocci] [PATCH 1/3] kobject: Add a jump label in kobject_uevent_env() Markus Elfring
2023-12-19 15:32 ` Markus Elfring
2023-12-19 15:34 ` [cocci] [PATCH 2/3] kobject: Improve a size determination " Markus Elfring
2023-12-19 15:34 ` Markus Elfring
2023-12-19 15:40 ` Greg Kroah-Hartman [this message]
2023-12-19 15:36 ` [cocci] [PATCH 3/3] kobject: Delete an unnecessary variable initialisation " Markus Elfring
2023-12-19 15:36 ` Markus Elfring
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=2023121946-immovable-striving-e2c7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 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.