From: Guenter Roeck <linux@roeck-us.net>
To: Jerry.Hoemann@hpe.com
Cc: wim@linux-watchdog.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] watchdog: hpwdt: Display module parameters.
Date: Mon, 6 Aug 2018 19:28:46 -0700 [thread overview]
Message-ID: <d1a220f1-e7ca-c4f5-9a2b-cbd622da536c@roeck-us.net> (raw)
In-Reply-To: <20180806231901.GA32467@anatevka.americas.hpqcorp.net>
On 08/06/2018 04:19 PM, Jerry Hoemann wrote:
> On Sat, Aug 04, 2018 at 06:13:20PM -0700, Guenter Roeck wrote:
>> On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
>>> Print module parameters when the driver is loaded.
>>>
>>> Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>
>>> ---
>>> drivers/watchdog/hpwdt.c | 5 +++--
>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
>>> index 8a85ddd..f098371 100644
>>> --- a/drivers/watchdog/hpwdt.c
>>> +++ b/drivers/watchdog/hpwdt.c
>>> @@ -326,8 +326,9 @@ static int hpwdt_init_one(struct pci_dev *dev,
>>> }
>>> dev_info(&dev->dev, "HPE Watchdog Timer Driver: %s"
>>> - ", timer margin: %d seconds (nowayout=%d).\n",
>>> - HPWDT_VERSION, hpwdt_dev.timeout, nowayout);
>>> + ", timeout : %d seconds (nowayout=%d) pretimeout=%s.\n",
>>> + HPWDT_VERSION, hpwdt_dev.timeout, nowayout,
>>> + pretimeout ? "on" : "off");
>> When touching that, you might as well address
>>
>> WARNING: quoted string split across lines
>
>
> k. Think I'll split into two dev_info calls as line is too long
> to fit into 80 chars w/o splitting.
>
>
>>
>> Why did you add a space before ':' ? Personal preference ?
>
> I think you're referring to "timeout : %d seconds". Bad editting when
> going from "timer margin:" to "timeout :". I'll fix.
>
Yes, that is what I referred to.
> If you referring to the spaces around the ternary operator, that is
> in coding-style although checkpatch accepts w/o spaces around the
> operators.
>
Nope, those spaces are desirable.
Guenter
next prev parent reply other threads:[~2018-08-07 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 21:15 [PATCH 0/4] watchdog: hpwdt: Bug Fixes/Enhancement Jerry Hoemann
2018-08-02 21:15 ` [PATCH 1/4] watchdog: hpwdt: Initialize pretimeout from module parameter Jerry Hoemann
2018-08-05 1:08 ` Guenter Roeck
2018-08-07 15:46 ` Jerry Hoemann
2018-08-02 21:15 ` [PATCH 2/4] watchdog: hpwdt: Claim NMI from iLO Jerry Hoemann
2018-08-05 1:09 ` Guenter Roeck
2018-08-08 19:12 ` Jerry Hoemann
2018-08-02 21:15 ` [PATCH 3/4] watchdog: hpwdt: Display module parameters Jerry Hoemann
2018-08-05 1:13 ` Guenter Roeck
2018-08-06 23:19 ` Jerry Hoemann
2018-08-07 2:28 ` Guenter Roeck [this message]
2018-08-02 21:15 ` [PATCH 4/4] watchdog: hpwdt: Update version number Jerry Hoemann
2018-08-05 1:16 ` Guenter Roeck
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=d1a220f1-e7ca-c4f5-9a2b-cbd622da536c@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Jerry.Hoemann@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®