From: Ira Weiny <ira.weiny@intel.com>
To: Sumitra Sharma <sumitraartsy@gmail.com>,
Julia Lawall <julia.lawall@inria.fr>
Cc: Marc Dietrich <marvin24@gmx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<ac100@lists.launchpad.net>, <linux-tegra@vger.kernel.org>,
<linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<outreachy@lists.linux.dev>
Subject: Re: [PATCH] Staging: nvec: Change container_of macro to an inline function.
Date: Mon, 20 Mar 2023 14:10:33 -0700 [thread overview]
Message-ID: <6418cbc98b225_2c274e29437@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230318175532.GA49651@sumitra.com>
Sumitra Sharma wrote:
> On Sat, Mar 18, 2023 at 06:14:50PM +0100, Julia Lawall wrote:
> >
> >
> > On Sat, 18 Mar 2023, Sumitra Sharma wrote:
> >
> > > The macro has the drawback that one cannot determine
> > > what type it applies to by looking at the definition.
> > > Hence this macro definition is not type-safe.
> > >
> > > The inline function gives the same benefits as the
> > > macro and only accepts the specific type of arguments.
> > > Use static because the definition only requires it to be
> > > visible in the current file.
> >
> > Sumitra,
> >
> > The subject line and log message could be a little less generic. For the
> > subject line, one has the impression that you are changing the definition
> > of container_of itself.
> >
> > The log message is also a bit wordy. Something like the following would
> > be more concise and still present the issue:
> >
>
> Okay. I will focus more on writing better patch subject and description.
Sumitra,
I can't tell for sure via email if you are getting discouraged. But if you are
don't feel bad. Writing good commit messages is hard.
That said, I see a couple of build errors from 0day on this patch. Do use the
tools to correct things like that before submitting.
Ira
next prev parent reply other threads:[~2023-03-20 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 17:05 [PATCH] Staging: nvec: Change container_of macro to an inline function Sumitra Sharma
2023-03-18 17:14 ` Julia Lawall
2023-03-18 17:55 ` Sumitra Sharma
2023-03-20 21:10 ` Ira Weiny [this message]
2023-03-18 18:55 ` kernel test robot
2023-03-18 20:48 ` kernel test robot
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=6418cbc98b225_2c274e29437@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=ac100@lists.launchpad.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
--cc=outreachy@lists.linux.dev \
--cc=sumitraartsy@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