From: Sean Whitton <spwhitton@spwhitton.name>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
~lkcamp/patches@lists.sr.ht, helen.koike@collabora.com,
Hans de Goede <hdegoede@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: media: atomisp: Add parentheses around macro definitions
Date: Sat, 03 Aug 2024 13:33:43 +0800 [thread overview]
Message-ID: <878qxe41c8.fsf@melete.silentflame.com> (raw)
In-Reply-To: <8d383b9d-d029-4706-91c5-9623fddf5df3@suswa.mountain> (Dan Carpenter's message of "Fri, 2 Aug 2024 23:28:43 -0500")
Hello,
On Fri 02 Aug 2024 at 11:28pm -05, Dan Carpenter wrote:
> *You* need to figure out what the proper thing is. Not us. That's the
> difficult part of writing a patch. Once you know what the correct thing
> is, then the rest is just typing.
>
> That business of defining STORAGE_CLASS_SP_C is weird. Figure out the
> authors intention and find a better way to do it.
>
> Figure out why your code compiled as well because putting parentheses
> around (static inline) is a syntax error.
I asked follow-up questions because it seems like at least partially a
matter of style to say that the business of defining STORAGE_CLASS_SP_C
is weird. Maybe there is a better approach than what is currently done,
but maybe there isn't. Maybe the checkpatch warning should just be
suppressed (if that's something that can be done). I would be grateful
for some additional pointers.
--
Sean Whitton
next prev parent reply other threads:[~2024-08-03 5:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 6:23 [PATCH] staging: media: atomisp: Add parentheses around macro definitions Sean Whitton
2024-07-30 6:38 ` Greg Kroah-Hartman
2024-08-03 3:28 ` Sean Whitton
2024-08-03 4:28 ` Dan Carpenter
2024-08-03 5:33 ` Sean Whitton [this message]
2024-08-03 6:10 ` Dan Carpenter
2024-08-04 3:36 ` Sean Whitton
2024-07-30 14:43 ` Dan Carpenter
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=878qxe41c8.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=helen.koike@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=~lkcamp/patches@lists.sr.ht \
/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