From: Lee Jones <lee@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Henning Schild <henning.schild@siemens.com>,
Pavel Machek <pavel@ucw.cz>, Mark Gross <markgross@kernel.org>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2/3] leds: simatic-ipc-leds-gpio: split up into multiple drivers
Date: Wed, 1 Mar 2023 16:06:09 +0000 [thread overview]
Message-ID: <Y/938WpvjQ3HEOwD@google.com> (raw)
In-Reply-To: <bf678bc5-9615-31a3-3039-5d013f9c9f25@redhat.com>
On Wed, 01 Mar 2023, Hans de Goede wrote:
> Hi,
>
> On 2/21/23 15:51, Andy Shevchenko wrote:
> > On Tue, Feb 21, 2023 at 03:43:54PM +0100, Henning Schild wrote:
> >> Am Tue, 21 Feb 2023 15:51:03 +0200
> >> schrieb Andy Shevchenko <andriy.shevchenko@linux.intel.com>:
> >>> On Tue, Feb 21, 2023 at 01:24:13PM +0100, Henning Schild wrote:
> >>>> In order to clearly describe the dependencies between the gpio
> >
> > ...
> >
> >>>> +#ifndef __DRIVERS_LEDS_SIMPLE_SIMATIC_IPC_LEDS_GPIO
> >>>> +#define __DRIVERS_LEDS_SIMPLE_SIMATIC_IPC_LEDS_GPIO
> >>>
> >>>> +#endif /* __DRIVERS_LEDS_SIMPLE_SIMATIC_IPC_LEDS_GPIO */
> >>>
> >>> This header doesn't look right.
> >>>
> >>> Have you run `make W=1 ...` against your patches?
> >>
> >> No reports.
> >>
> >>> Even if it doesn't show defined but unused errors
> >>> the idea is that this should be a C-file, called,
> >>> let's say, ...-core.c.
> >>
> >> When i started i kind of had a -common.c in mind as well. But then the
> >> header idea came and i gave it a try, expecting questions in the review.
> >>
> >> It might be a bit unconventional but it seems to do the trick pretty
> >> well. Do you see a concrete problem or a violation of a rule?
> >
> > Exactly as described above. The header approach means that *all* static
> > definitions must be used by each user of that file. Otherwise you will
> > get "defined but not used" compiler warning.
> >
> > And approach itself is considered (at least by me) as a hackish way to
> > achieve what usually should be done via C-file.
> >
> > So, if maintainers are okay, I wouldn't have objections, but again
> > I do not think it's a correct approach.
>
> I agree with Andy here, please add a -common.o file with a shared
> probe() helper which gets the 2 different gpiod_lookup_table-s
> as parameter and then put the actual probe() function calling
> the helper inside the 2 different .c files.
Thanks for your reviews guys, I really appreciate the help.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-03-01 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:24 [PATCH 0/3] leds: simatic-ipc-leds-gpio: split up Henning Schild
2023-02-21 12:24 ` [PATCH 1/3] leds: simatic-ipc-leds-gpio: move two extra gpio pins into another table Henning Schild
2023-02-21 13:45 ` Andy Shevchenko
2023-02-21 12:24 ` [PATCH 2/3] leds: simatic-ipc-leds-gpio: split up into multiple drivers Henning Schild
2023-02-21 13:51 ` Andy Shevchenko
2023-02-21 14:43 ` Henning Schild
2023-02-21 14:51 ` Andy Shevchenko
2023-03-01 14:53 ` Hans de Goede
2023-03-01 16:06 ` Lee Jones [this message]
2023-03-01 16:45 ` Andy Shevchenko
2023-03-01 16:53 ` Henning Schild
2023-02-21 12:24 ` [PATCH 3/3] leds: simatic-ipc-leds-gpio: introduce more Kconfig switches Henning Schild
2023-02-21 13:52 ` Andy Shevchenko
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=Y/938WpvjQ3HEOwD@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=henning.schild@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.