From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: "Michał Kępień" <kernel@kempniu.pl>, "Joe Perches" <joe@perches.com>
Cc: "Richard Purdie" <rpurdie@rpsys.net>,
"Pavel Machek" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Darren Hart" <dvhart@infradead.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Anthony Wong" <anthony.wong@canonical.com>,
linux-leds@vger.kernel.org, platform-driver-x86@vger.kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6+/6] platform/x86: dell-wmi-led: fix coding style issues
Date: Tue, 17 Jan 2017 22:20:39 +0100 [thread overview]
Message-ID: <b19ccd46-d5ac-b02e-f5c3-2d953588303b@gmail.com> (raw)
In-Reply-To: <20170117091925.GA1042@ozzy.nask.waw.pl>
Hi Michał,
On 01/17/2017 10:19 AM, Michał Kępień wrote:
>> On Tue, 2017-01-17 at 08:17 +0100, Michał Kępień wrote:
>>> Fix coding style issues in dell-wmi-led which checkpatch complains about
>>> to make sure the module gets a clean start in the x86 platform driver
>>> subsystem.
>>
>> trivia:
>>
>>> Signed-off-by: Michał Kępień <kernel@kempniu.pl>
>>> ---
>>> This is an extra patch that Jacek asked for [1].
>>>
>>> [1] https://lkml.org/lkml/2017/1/16/631
>>>
>>> drivers/platform/x86/dell-wmi-led.c | 41 +++++++++++++++----------------------
>>> 1 file changed, 16 insertions(+), 25 deletions(-)
>>>
>>> diff --git a/drivers/platform/x86/dell-wmi-led.c b/drivers/platform/x86/dell-wmi-led.c
>> []
>>> @@ -46,21 +46,16 @@ struct bios_args {
>>> unsigned char off_time;
>>> };
>>>
>>> -static int dell_led_perform_fn(u8 length,
>>> - u8 result_code,
>>> - u8 device_id,
>>> - u8 command,
>>> - u8 on_time,
>>> - u8 off_time)
>>> +static int dell_led_perform_fn(u8 length, u8 result_code, u8 device_id,
>>> + u8 command, u8 on_time, u8 off_time)
>>> {
>>> - struct bios_args *bios_return;
>>> - u8 return_code;
>>> - union acpi_object *obj;
>>> struct acpi_buffer output = { ACPI_ALLOCATE_BUFFER, NULL };
>>> + struct bios_args *bios_return, args;
>>> struct acpi_buffer input;
>>> + union acpi_object *obj;
>>> acpi_status status;
>>> + u8 return_code;
>>>
>>> - struct bios_args args;
>>> args.length = length;
>>> args.result_code = result_code;
>>> args.device_id = device_id;
>>
>> This declaration might be nicer using
>>
>> struct bios_args args = {
>> .length = length,
>> .result_code = result_code,
>> .device_id = device_id,
>> [...]
>> };
>>
>> []
>>
>>> @@ -138,24 +128,25 @@ static void dell_led_set(struct led_classdev *led_cdev,
>>> }
>>>
>>> static int dell_led_blink(struct led_classdev *led_cdev,
>>> - unsigned long *delay_on,
>>> - unsigned long *delay_off)
>>> + unsigned long *delay_on, unsigned long *delay_off)
>>> {
>>> unsigned long on_eighths;
>>> unsigned long off_eighths;
>>>
>>> - /* The Dell LED delay is based on 125ms intervals.
>>> - Need to round up to next interval. */
>>> + /*
>>> + * The Dell LED delay is based on 125ms intervals.
>>> + * Need to round up to next interval.
>>> + */
>>>
>>> on_eighths = (*delay_on + 124) / 125;
>>> - if (0 == on_eighths)
>>> + if (on_eighths == 0)
>>> on_eighths = 1;
>>> if (on_eighths > 255)
>>> on_eighths = 255;
>>> *delay_on = on_eighths * 125;
>>>
>>> off_eighths = (*delay_off + 124) / 125;
>>> - if (0 == off_eighths)
>>> + if (off_eighths == 0)
>>> off_eighths = 1;
>>> if (off_eighths > 255)
>>> off_eighths = 255;
>>
>> These could use DIV_ROUND_UP and clamp()
>
> Thanks for taking a look, Joe, I can certainly fix these.
>
> Jacek, as resending an updated version of this patch with Joe's
> suggestions taken into account would be even more confusing than the
> "PATCH v2 6+/6" subject I already resorted to, I suggest the following:
> if this series goes to v3, I will include an updated version of this
> patch in v3, but in case the remaining patches get acked in their
> current shape by all maintainers, I will send an updated version of this
> extra patch separately, after the rest of the series gets applied. Does
> this sound reasonable?
Sure. I'll merge whole patch set after getting acks from sound
and x86 platform drivers maintainers.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2017-01-17 21:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 13:21 [PATCH v2 0/6] Move dell-led to drivers/platform/x86 Michał Kępień
2017-01-16 13:21 ` [PATCH v2 1/6] dell-led: remove GUID check from dell_micmute_led_set() Michał Kępień
2017-01-16 13:22 ` [PATCH v2 2/6] ALSA: hda - use dell_micmute_led_set() instead of dell_app_wmi_led_set() Michał Kępień
2017-01-16 13:22 ` [PATCH v2 3/6] ALSA: hda - rename dell_led_set_func to dell_micmute_led_set_func Michał Kępień
2017-01-17 11:12 ` Pali Rohár
2017-01-17 21:20 ` Jacek Anaszewski
2017-01-16 13:22 ` [PATCH v2 4/6] platform/x86: dell-laptop: import dell_micmute_led_set() from drivers/leds/dell-led.c Michał Kępień
2017-01-17 11:23 ` Pali Rohár
2017-01-18 19:12 ` Andy Shevchenko
2017-01-16 13:22 ` [PATCH v2 5/6] dell-led: remove code related to mic mute LED Michał Kępień
2017-01-17 11:24 ` Pali Rohár
2017-01-16 13:22 ` [PATCH v2 6/6] dell-led: move driver to drivers/platform/x86/dell-wmi-led.c Michał Kępień
2017-01-16 20:49 ` Jacek Anaszewski
2017-01-17 11:08 ` Pavel Machek
2017-01-17 11:28 ` Pali Rohár
2017-01-18 19:08 ` Andy Shevchenko
2017-01-17 7:17 ` [PATCH v2 6+/6] platform/x86: dell-wmi-led: fix coding style issues Michał Kępień
2017-01-17 8:21 ` Joe Perches
2017-01-17 9:19 ` Michał Kępień
2017-01-17 21:20 ` Jacek Anaszewski [this message]
2017-01-17 11:08 ` Pavel Machek
2017-01-18 19:06 ` Andy Shevchenko
2017-01-17 21:20 ` [PATCH v2 0/6] Move dell-led to drivers/platform/x86 Jacek Anaszewski
2017-02-13 11:26 ` Michał Kępień
2017-02-15 11:56 ` Alex Hung
2017-02-15 13:54 ` Michał Kępień
2017-02-15 14:31 ` Alex Hung
2017-02-15 15:12 ` Pali Rohár
2017-02-16 9:33 ` Michał Kępień
2017-02-16 9:27 ` Michał Kępień
2017-02-16 10:35 ` Alex Hung
2017-02-16 11:32 ` Michał Kępień
2017-02-16 11:38 ` Alex Hung
2017-02-16 11:41 ` Andy Shevchenko
2017-02-16 12:01 ` Michał Kępień
2017-02-16 13:11 ` Andy Shevchenko
2017-02-16 22:11 ` Jacek Anaszewski
2017-02-15 20:28 ` Takashi Iwai
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=b19ccd46-d5ac-b02e-f5c3-2d953588303b@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=andy.shevchenko@gmail.com \
--cc=anthony.wong@canonical.com \
--cc=dvhart@infradead.org \
--cc=joe@perches.com \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=perex@perex.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).