From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Dan Carpenter <error27@gmail.com>
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 v2] Staging: nvec: Convert to_nvec_led from a macro to an inline function
Date: Mon, 20 Mar 2023 01:44:22 -0700 [thread overview]
Message-ID: <20230320084422.GA126429@sumitra.com> (raw)
In-Reply-To: <417e944c-4653-43ef-b492-c82c536e4d87@kili.mountain>
On Mon, Mar 20, 2023 at 08:39:49AM +0300, Dan Carpenter wrote:
> On Sat, Mar 18, 2023 at 10:52:50AM -0700, Sumitra Sharma wrote:
> > Convert to_nvec_led from a macro to a static inline function, to make the
> > relevant types apparent in the definition and to benefit from the type
> > checking performed by the compiler at call sites.
> >
> > Signed-off-by: Sumitra Sharma <sumitraartsy@gmail.com>
> > ---
>
> You need to compile test your changes.
>
Hi dan,
I am facing problems in creating modules and in compiling them.
Any help in this would be appreciated. Here is the link to the thread https://lore.kernel.org/outreachy/alpine.DEB.2.22.394.2303191336090.2867@hadrien/T/#t
Regards,
Sumitra
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2023-03-20 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 17:52 [PATCH v2] Staging: nvec: Convert to_nvec_led from a macro to an inline function Sumitra Sharma
2023-03-20 5:39 ` Dan Carpenter
2023-03-20 8:44 ` Sumitra Sharma [this message]
2023-03-20 8:58 ` Dan Carpenter
2023-03-20 9:07 ` Julia Lawall
2023-03-20 15:27 ` kernel test robot
2023-03-20 15:45 ` Greg Kroah-Hartman
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=20230320084422.GA126429@sumitra.com \
--to=sumitraartsy@gmail.com \
--cc=ac100@lists.launchpad.net \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).