From: Guenter Roeck <linux@roeck-us.net>
To: "Croxon, Nigel" <nigel.croxon@hpe.com>,
"wim@iguana.be" <wim@iguana.be>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH V3] watchdog: hpwdt: Adjust documentation to match latest kernel module parameters
Date: Thu, 7 Apr 2016 18:06:41 -0700 [thread overview]
Message-ID: <57070421.4070603@roeck-us.net> (raw)
In-Reply-To: <A4930445748CDC43B8495613130746F44ECEC789@G4W3214.americas.hpqcorp.net>
On 04/06/2016 06:11 PM, Croxon, Nigel wrote:
> From: Nigel Croxon <nigel.croxon@hpe.com>
> Date: Wed, 6 Apr 2016 14:40:05 -0400
> Subject: [PATCH V3] watchdog: hpwdt: Adjust documentation to match latest kernel module parameters.
>
> Adjust documentation to match latest kernel module parameters.
>
> V3 - Fixed two spelling mistakes.
> V2 - Changed insmod / rmmod to modprobe / modprobe -r
>
> Signed-off-by: Nigel Croxon <nigel.croxon@hpe.com>
Nigel,
when applying this patch:
Applying: watchdog: hpwdt: Adjust documentation to match latest kernel module parameters.
/home/groeck/src/linux-staging/.git/rebase-apply/patch:75: trailing whitespace.
the hpwdt driver can be reloaded.
/home/groeck/src/linux-staging/.git/rebase-apply/patch:92: trailing whitespace.
4. modprobe /lib/modules/`uname -r`/kernel/drivers/watchdog/hpwdt.ko
warning: 2 lines add whitespace errors.
Please fix and resubmit.
FWIW, those whitespace errors are also reported with checkpatch.
Thanks,
Guenter
prev parent reply other threads:[~2016-04-08 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 1:11 [PATCH V3] watchdog: hpwdt: Adjust documentation to match latest kernel module parameters Croxon, Nigel
2016-04-07 13:12 ` Guenter Roeck
2016-04-08 1:06 ` Guenter Roeck [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=57070421.4070603@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=nigel.croxon@hpe.com \
--cc=wim@iguana.be \
/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.