From: Greg KH <gregkh@linuxfoundation.org>
To: Madhumitha Prabakaran <madhumithabiw@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, greybus-dev@lists.linaro.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Staging: greybus: Cleanup in greybus driver
Date: Wed, 17 Apr 2019 08:25:18 +0200 [thread overview]
Message-ID: <20190417062518.GA23076@kroah.com> (raw)
In-Reply-To: <20190416221318.21161-1-madhumithabiw@gmail.com>
On Tue, Apr 16, 2019 at 05:13:18PM -0500, Madhumitha Prabakaran wrote:
> Fix a blank line after structure declarations. Also, convert
> macros into inline functions in order to maintain Linux kernel
> coding style based on which the inline function is
> preferable over the macro.
>
> Blank line fixes are suggested by checkpatch.pl
>
> Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
>
> Changes in v2:
> - To maintain consistency in driver greybus, all the instances of macro
> with container_of are fixed in a single patch.
> ---
> drivers/staging/greybus/bundle.h | 6 +++++-
> drivers/staging/greybus/control.h | 6 +++++-
> drivers/staging/greybus/gbphy.h | 12 ++++++++++--
> drivers/staging/greybus/greybus.h | 6 +++++-
> drivers/staging/greybus/hd.h | 6 +++++-
> drivers/staging/greybus/interface.h | 6 +++++-
> drivers/staging/greybus/module.h | 6 +++++-
> drivers/staging/greybus/svc.h | 6 +++++-
> 8 files changed, 45 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/greybus/bundle.h b/drivers/staging/greybus/bundle.h
> index 8734d2055657..84956eedb1c4 100644
> --- a/drivers/staging/greybus/bundle.h
> +++ b/drivers/staging/greybus/bundle.h
> @@ -31,7 +31,11 @@ struct gb_bundle {
>
> struct list_head links; /* interface->bundles */
> };
> -#define to_gb_bundle(d) container_of(d, struct gb_bundle, dev)
> +
> +static inline struct gb_bundle *to_gb_bundle(struct device *d)
> +{
> + return container_of(d, struct gb_bundle, dev);
> +}
Why are we changing this to an inline function? The #define is fine,
and how we "normally" do this type of container_of conversion.
I understand the objection of the "no blank line", but this was the
"original" style that we used to create these #defines from the very
beginning of the driver model work a decade ago. Changing that
muscle-memory is going to be hard for some of us. Look at
drivers/base/base.h for other examples of this.
thanks,
greg k-h
next prev parent reply other threads:[~2019-04-17 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 22:13 [PATCH v2] Staging: greybus: Cleanup in greybus driver Madhumitha Prabakaran
2019-04-17 2:11 ` [greybus-dev] " Viresh Kumar
2019-04-17 6:25 ` Greg KH [this message]
2019-04-17 11:19 ` Alex Elder
2019-04-17 11:39 ` Johan Hovold
2019-04-18 0:55 ` Madhumitha Prabakaran
2019-04-17 11:41 ` [greybus-dev] " Alex Elder
2019-04-18 0:58 ` Madhumitha Prabakaran
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=20190417062518.GA23076@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhumithabiw@gmail.com \
/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