From: Julia Lawall <julia.lawall@inria.fr>
To: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
Cc: gregkh@linuxfoundation.org, outreachy@lists.linux.dev,
namcaov@gmail.com, straube.linux@gmail.com, hdegoede@redhat.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: include: use inline functions for dvobj_to_dev
Date: Sun, 19 Mar 2023 15:13:04 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2303191509330.2867@hadrien> (raw)
In-Reply-To: <20230319131030.151170-3-eng.mennamahmoud.mm@gmail.com>
How have you chosen the names at the beginning of the subject line? The
other patches on this file don't have the word "include:" in the subject.
Please see the section "Following the Driver commit style" of the tutorial
to see what to do.
On Sun, 19 Mar 2023, Menna Mahmoud wrote:
> Convert `dvobj_to_dev` macro into static inline function,
"into a static inline function"
But the message is a bit too verbose. Please see my suggestion on another
similar patch that was recently proposed.
julia
> because 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 (concretely, typically a static inline function, because
> the definition only needs to be visible in the current file, or in the
> case of a header file in the file that includes the header file).
>
> Suggested-by: Julia Lawall <julia.lawall@inria.fr>
> Signed-off-by: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
> ---
> drivers/staging/rtl8723bs/include/drv_types.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/include/drv_types.h b/drivers/staging/rtl8723bs/include/drv_types.h
> index 82159e1c7f9b..ea6bb44c5e1d 100644
> --- a/drivers/staging/rtl8723bs/include/drv_types.h
> +++ b/drivers/staging/rtl8723bs/include/drv_types.h
> @@ -305,7 +305,11 @@ struct sdio_data intf_data;
> };
>
> #define dvobj_to_pwrctl(dvobj) (&(dvobj->pwrctl_priv))
> -#define pwrctl_to_dvobj(pwrctl) container_of(pwrctl, struct dvobj_priv, pwrctl_priv)
> +
> +static inline struct dvobj_priv *pwrctl_to_dvobj(struct pwrctrl_priv *pwrctl_priv)
> +{
> + return container_of(pwrctl_priv, struct dvobj_priv, pwrctl_priv);
> +}
>
> static inline struct device *dvobj_to_dev(struct dvobj_priv *dvobj)
> {
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-03-19 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 13:10 Menna Mahmoud
2023-03-19 14:13 ` Julia Lawall [this message]
2023-03-19 14:34 ` 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.2303191509330.2867@hadrien \
--to=julia.lawall@inria.fr \
--cc=eng.mennamahmoud.mm@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@gmail.com \
--cc=outreachy@lists.linux.dev \
--cc=straube.linux@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
all inboxes | Powered by JetHome®