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, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH] staging: greybus: use inline function for macros
Date: Sun, 19 Mar 2023 21:21:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2303192121170.2867@hadrien> (raw)
In-Reply-To: <20230319201324.253874-1-eng.mennamahmoud.mm@gmail.com>
On Sun, 19 Mar 2023, Menna Mahmoud wrote:
> Convert `to_gbphy_dev` and `to_gbphy_driver` macros into a
> static inline functions.
>
> it is not great to have macro that use `container_of` macro,
> because from looking at the definition one cannot tell what type
> it applies to.
>
> One can get the same benefit from an efficiency point of view
> by making an inline function.
>
> Suggested-by: Julia Lawall <julia.lawall@inria.fr>
> Signed-off-by: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
> ---
> drivers/staging/greybus/gbphy.h | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/gbphy.h b/drivers/staging/greybus/gbphy.h
> index 1de510499480..42c4e3fe307c 100644
> --- a/drivers/staging/greybus/gbphy.h
> +++ b/drivers/staging/greybus/gbphy.h
> @@ -16,7 +16,10 @@ struct gbphy_device {
> struct device dev;
> };
>
You have made the patch against your previous patch that added a newline
here. It should be against Greg's tree.
julia
> -#define to_gbphy_dev(d) container_of(d, struct gbphy_device, dev)
> +static inline struct gbphy_device *to_gbphy_dev(const struct device *d)
> +{
> + return container_of(d, struct gbphy_device, dev);
> +}
>
> static inline void *gb_gbphy_get_data(struct gbphy_device *gdev)
> {
> @@ -45,7 +48,10 @@ struct gbphy_driver {
> struct device_driver driver;
> };
>
> -#define to_gbphy_driver(d) container_of(d, struct gbphy_driver, driver)
> +static inline struct gbphy_driver *to_gbphy_driver(struct device_driver *d)
> +{
> + return container_of(d, struct gbphy_driver, driver);
> +}
>
> int gb_gbphy_register_driver(struct gbphy_driver *driver,
> struct module *owner, const char *mod_name);
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-03-19 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 20:13 Menna Mahmoud
2023-03-19 20:21 ` Julia Lawall [this message]
2023-03-19 20:42 ` Menna Mahmoud
2023-03-19 20:55 ` Julia Lawall
2023-03-19 21:07 ` Menna Mahmoud
2023-03-19 21:26 ` Julia Lawall
2023-03-19 22:00 ` Menna Mahmoud
2023-03-19 22:06 ` Julia Lawall
2023-03-19 22:17 ` Menna Mahmoud
2023-03-20 6:00 ` Julia Lawall
2023-03-20 10:14 ` 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.2303192121170.2867@hadrien \
--to=julia.lawall@inria.fr \
--cc=elder@kernel.org \
--cc=eng.mennamahmoud.mm@gmail.com \
--cc=gregkh@linuxfoundation.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®