mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
Cc: gregkh@linuxfoundation.org, outreachy@lists.linux.dev,
	johan@kernel.org, elder@kernel.org, greybus-dev@lists.linaro.org,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: add blank line after struct
Date: Sun, 19 Mar 2023 12:46:41 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2303191246190.2867@hadrien> (raw)
In-Reply-To: <6cc1e2f7-e971-b195-acba-9b4c136aa16b@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2817 bytes --]



On Sun, 19 Mar 2023, Menna Mahmoud wrote:

>
> On ١٩/٣/٢٠٢٣ ١٣:٣٦, Julia Lawall wrote:
> >
> > On Sun, 19 Mar 2023, Menna Mahmoud wrote:
> >
> > > On ١٩/٣/٢٠٢٣ ١٣:١٩, Julia Lawall wrote:
> > > > On Sun, 19 Mar 2023, Menna Mahmoud wrote:
> > > >
> > > > > add blank line after struct for readability as
> > > > The log message should start with a capital letter, so "Add".
> > >
> > > Okay, I will fix it.
> > >
> > > > > reported by checkpatch script
> > > > "reported by checkpatch" or "reported by the checkpatch script".
> > > > The first is more concise, and it doesn't really matter whether
> > > > checkpatch
> > > > is a script or something else.
> > >
> > > got it.
> > >
> > > > > " CHECK: Please use a blank line after function/struct/union/enum
> > > > > declarations"
> > > > I guess the #define was concatenated to the end of the definition to
> > > > show
> > > > that it is closely related to the definition.  With the #define, it
> > > > seems
> > > > rather natural, but the better soltution would be to make a static
> > > > inline
> > > > function in both cases.  There would naturally be a blank line before a
> > > > function definition as well.
> > >
> > > got your point, so, should i ignore this?
> > Not sure what you mean by ignore.  If you rewrite the #define as a
> > function, an use the natural placement for a function definition, then the
> > checkpatch warning will go away as a side effect.
>
>
> I mean ignore this patch and make another patch with rewrite #define as you
> suggested.

Yes :)  That's fine ("drop" would be better than "ignore").

julia

>
>
> Menna
>
> >
> > julia
> >
> > >
> > > Menna
> > >
> > > > julia
> > > >
> > > > > Signed-off-by: Menna Mahmoud <eng.mennamahmoud.mm@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.34.1
> > > > >
> > > > >
> > > > >
> > >
>

  reply	other threads:[~2023-03-19 11:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 11:08 Menna Mahmoud
2023-03-19 11:19 ` Julia Lawall
2023-03-19 11:28   ` Menna Mahmoud
2023-03-19 11:36     ` Julia Lawall
2023-03-19 11:41       ` Menna Mahmoud
2023-03-19 11:46         ` Julia Lawall [this message]
2023-03-19 11:52           ` Menna Mahmoud
2023-03-19 11:41 Menna Mahmoud
2023-03-19 13:20 ` Menna Mahmoud

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=alpine.DEB.2.22.394.2303191246190.2867@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=elder@kernel.org \
    --cc=eng.mennamahmoud.mm@gmail.com \
    --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=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®