From: Julia Lawall <julia.lawall@inria.fr>
To: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
Cc: gregkh@linuxfoundation.org, outreachy@lists.linux.dev,
parthiban.veerasooran@microchip.com,
christian.gromm@microchip.com, drv@mailo.com, dave@stgolabs.net,
yang.lee@linux.alibaba.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH v2] staging: most: use inline functions for iface_to_hdm
Date: Mon, 20 Mar 2023 22:17:45 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2303202217110.2906@hadrien> (raw)
In-Reply-To: <20230320205207.20062-1-eng.mennamahmoud.mm@gmail.com>
Maybe "define iface_to_hdm as an inline function" would be better. "use"
is not very precise.
julia
On Mon, 20 Mar 2023, Menna Mahmoud wrote:
> Convert `iface_to_hdm` macro into a static inline function.
> 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>
> ---
> change in v2:
> edit subject line.
> ---
> drivers/staging/most/dim2/dim2.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/most/dim2/dim2.c b/drivers/staging/most/dim2/dim2.c
> index b8bd01ca1f11..21d1c9f24c3d 100644
> --- a/drivers/staging/most/dim2/dim2.c
> +++ b/drivers/staging/most/dim2/dim2.c
> @@ -108,7 +108,10 @@ struct dim2_platform_data {
> u8 fcnt;
> };
>
> -#define iface_to_hdm(iface) container_of(iface, struct dim2_hdm, most_iface)
> +static inline struct dim2_hdm *iface_to_hdm(struct most_interface *iface)
> +{
> + return container_of(iface, struct dim2_hdm, most_iface);
> +}
>
> /* Macro to identify a network status message */
> #define PACKET_IS_NET_INFO(p) \
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-03-20 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 20:52 Menna Mahmoud
2023-03-20 21:17 ` Julia Lawall [this message]
2023-03-20 21:19 ` 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.2303202217110.2906@hadrien \
--to=julia.lawall@inria.fr \
--cc=christian.gromm@microchip.com \
--cc=dave@stgolabs.net \
--cc=drv@mailo.com \
--cc=eng.mennamahmoud.mm@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=parthiban.veerasooran@microchip.com \
--cc=yang.lee@linux.alibaba.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®