linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Gamari <bgamari.foss@gmail.com>
To: Bryan Wu <cooloney@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>
Subject: Re: [PATCH] leds/leds-pwm: Display error code on request_pwm failure
Date: Mon, 16 Dec 2013 23:05:34 -0500	[thread overview]
Message-ID: <87vbyoyve9.fsf@gmail.com> (raw)
In-Reply-To: <CAK5ve-Jteb3UcBAhT6qJ=ZOwpzSw04iZGHkOofYkua3tfKdHQw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]

Bryan Wu <cooloney@gmail.com> writes:

> On Mon, Dec 16, 2013 at 5:26 PM, Bryan Wu <cooloney@gmail.com> wrote:
>> On Mon, Dec 16, 2013 at 4:08 PM, Ben Gamari <bgamari.foss@gmail.com> wrote:
>>> This can be useful in debugging devicetrees.
>>>
>>
>> OK, I will merge this.
>>
>
>
>> Thanks,
>> -Bryan
>>
>>> Signed-off-by: Ben Gamari <bgamari.foss@gmail.com>
>>> ---
>>>  drivers/leds/leds-pwm.c | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/leds/leds-pwm.c b/drivers/leds/leds-pwm.c
>>> index b31d8e9..707a82a 100644
>>> --- a/drivers/leds/leds-pwm.c
>>> +++ b/drivers/leds/leds-pwm.c
>>> @@ -165,8 +165,8 @@ static int led_pwm_probe(struct platform_device *pdev)
>>>                         if (IS_ERR(led_dat->pwm)) {
>>>                                 ret = PTR_ERR(led_dat->pwm);
>>>                                 dev_err(&pdev->dev,
>>> -                                       "unable to request PWM for %s\n",
>>> -                                       cur_led->name);
>>> +                                       "unable to request PWM for %s: error=%d\n",
>
> Oh, hold on, this line has more than 80 characters. Please fix this
> coding style error.
>
Would this not fall under the "unless" clause of the kernel style guidelines,

    Statements longer than 80 columns will be broken into sensible chunks, unless
    exceeding 80 columns significantly increases readability and does not hide
    information.

The line is 82 characters long by my count and there is no reasonable
way to break it. The only fix I can think of here is to introduce a
local variable for the format string but in my opinion this is far less
readable than what we currently have. Which would you prefer?

Cheers,

- Ben

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

      reply	other threads:[~2013-12-17  4:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  0:08 [PATCH] leds/leds-pwm: Display error code on request_pwm failure Ben Gamari
2013-12-17  1:26 ` Bryan Wu
2013-12-17  1:28   ` Bryan Wu
2013-12-17  4:05     ` Ben Gamari [this message]

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=87vbyoyve9.fsf@gmail.com \
    --to=bgamari.foss@gmail.com \
    --cc=cooloney@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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).