From: Julia Lawall <julia.lawall@inria.fr>
To: Okhuomon Ajayi <okhuomonajayi54@gmail.com>
Cc: outreachy@lists.linux.dev, Johan Hovold <johan@kernel.org>,
Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: add blank lines after struct definitions in gbphy.h
Date: Thu, 15 Oct 2026 22:17:35 -0400 (EDT) [thread overview]
Message-ID: <fcdee571-d94c-a5ae-5ae5-b41977f22073@inria.fr> (raw)
In-Reply-To: <20261015222735.89251-1-okhuomonajayi54@gmail.com>
On Thu, 15 Oct 2026, Okhuomon Ajayi wrote:
> Add blank lines between the structure definitions and the
> to_gbphy_dev() and to_gbphy_driver() macros to improve
> readability. This fixes the following checkpatch warning:
Thanks for the patch. But I suspect that the lack of a newline was
intentional, to show that the #define is closely associated with the
previous structure declaration.
julia
>
> CHECK: Please use a blank line after function/struct/union/enum
> declarations
>
> Signed-off-by: Okhuomon Ajayi <okhuomonajayi54@gmail.com>
> ---
> drivers/staging/greybus/gbphy.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/greybus/gbphy.h b/drivers/staging/greybus/gbphy.h
> index d4a225b76338..1de510499480 100644
> --- a/drivers/staging/greybus/gbphy.h
> +++ b/drivers/staging/greybus/gbphy.h
> @@ -15,6 +15,7 @@ struct gbphy_device {
> struct list_head list;
> struct device dev;
> };
> +
> #define to_gbphy_dev(d) container_of(d, struct gbphy_device, dev)
>
> static inline void *gb_gbphy_get_data(struct gbphy_device *gdev)
> @@ -43,6 +44,7 @@ struct gbphy_driver {
>
> struct device_driver driver;
> };
> +
> #define to_gbphy_driver(d) container_of(d, struct gbphy_driver, driver)
>
> int gb_gbphy_register_driver(struct gbphy_driver *driver,
> --
> 2.43.0
>
>
>
next prev parent reply other threads:[~2026-10-16 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 22:27 Okhuomon Ajayi
2026-10-16 2:17 ` Julia Lawall [this message]
2026-10-16 4:55 ` Greg Kroah-Hartman
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=fcdee571-d94c-a5ae-5ae5-b41977f22073@inria.fr \
--to=julia.lawall@inria.fr \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=okhuomonajayi54@gmail.com \
--cc=outreachy@lists.linux.dev \
/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®