From: "Michał Kępień" <kernel@kempniu.pl>
To: Jonathan Woithe <jwoithe@just42.net>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] platform/x86: fujitsu-laptop: register backlight device in a separate function
Date: Fri, 10 Mar 2017 11:45:24 +0100 [thread overview]
Message-ID: <20170310104524.GC13521@ozzy.nask.waw.pl> (raw)
In-Reply-To: <20170310104210.GB21396@marvin.atrad.com.au>
> Hi Michael
>
> On Fri, Mar 10, 2017 at 10:08:49AM +0100, Micha?? K??pie?? wrote:
> > > Move code responsible for backlight device registration to a separate
> > > function in order to simplify error handling and decrease indentation.
> > > Simplify initialization of struct backlight_properties. Use
> > > KBUILD_MODNAME as device name to avoid repeating the same string literal
> > > throughout the module.
> > >
> > > Signed-off-by: Micha?? K??pie?? <kernel@kempniu.pl>
> > > ---
> > > drivers/platform/x86/fujitsu-laptop.c | 38 ++++++++++++++++++++---------------
> > > 1 file changed, 22 insertions(+), 16 deletions(-)
> > >
> > > diff --git a/drivers/platform/x86/fujitsu-laptop.c b/drivers/platform/x86/fujitsu-laptop.c
> > > index e12cc3504d48..185c929898d9 100644
> > > --- a/drivers/platform/x86/fujitsu-laptop.c
> > > +++ b/drivers/platform/x86/fujitsu-laptop.c
> > > @@ -685,6 +685,25 @@ static const struct dmi_system_id fujitsu_dmi_table[] __initconst = {
> > >
> > > /* ACPI device for LCD brightness control */
> > >
> > > +static int fujitsu_backlight_register(void)
> > > +{
> > > + struct backlight_properties props = {
> > > + .brightness = fujitsu_bl->brightness_level,
> > > + .max_brightness = fujitsu_bl->max_brightness - 1,
> > > + .type = BACKLIGHT_PLATFORM
> > > + };
> > > + struct backlight_device *bd;
> > > +
> > > + bd = backlight_device_register(KBUILD_MODNAME, NULL, NULL,
> > > + &fujitsu_bl_ops, &props);
> >
> > I have only just now noticed that this effectively breaks userspace
> > interface as KBUILD_MODNAME is "fujitsu_laptop" while the previously
> > used device name was "fujitsu-laptop" (underscore vs. hyphen).
>
> Ah yes, I noticed that too, as you see from the review I just sent through.
> Sorry, I didn't see the above post until after I'd sent the review in. It's
> no big deal though.
>
> > Jonathan, as this series is already long overdue, I suggest the
> > following course of action: please review these patches anyway and if
> > you find no other issues, please provide your Reviewed-by etc. as you
> > normally would. Once you do that, I will post v4 which will use
> > "fujitsu-laptop" for backlight device name and will contain your v3
> > review tags. Does that sound reasonable?
>
> As per my review comments, I am happy with the patch series so long as the
> backlight device name reverts to "fujitsu-laptop". Your suggested course of
> action sounds fine to me. Alternatively, I could quickly and easily add
> tags to a v4 post if that is seen to be more appropriate by Darren/Andy.
> I'm easy either way.
Sure, we can do it this way as well. I will post v4 shortly.
--
Best regards,
Michał Kępień
next prev parent reply other threads:[~2017-03-10 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 10:15 [PATCH v3 0/4] fujitsu_init() cleanup Michał Kępień
2017-03-07 10:15 ` [PATCH v3 1/4] platform/x86: fujitsu-laptop: register backlight device in a separate function Michał Kępień
2017-03-10 9:08 ` Michał Kępień
2017-03-10 10:42 ` Jonathan Woithe
2017-03-10 10:45 ` Michał Kępień [this message]
2017-03-07 10:15 ` [PATCH v3 2/4] platform/x86: fujitsu-laptop: sync backlight power status in acpi_fujitsu_laptop_add() Michał Kępień
2017-03-07 10:15 ` [PATCH v3 3/4] platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present Michał Kępień
2017-03-07 10:15 ` [PATCH v3 4/4] platform/x86: fujitsu-laptop: cleanup error labels in fujitsu_init() Michał Kępień
2017-03-08 6:49 ` [PATCH v3 0/4] fujitsu_init() cleanup Jonathan Woithe
2017-03-10 10:34 ` Jonathan Woithe
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=20170310104524.GC13521@ozzy.nask.waw.pl \
--to=kernel@kempniu.pl \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=jwoithe@just42.net \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox