From: Jason Cooper <jason@lakedaemon.net>
To: Andreas Siegling <andreas.siegling@fau.de>
Cc: devel@linuxdriverproject.org, gregkh@linuxfoundation.org,
eric.rost@mybabylon.net, nks@flawful.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-kernel@i4.cs.fau.de, trivial@kernel.org,
Zhutao Lu <lvzhutao@gmail.com>
Subject: Re: [PATCH] skein: checkpatch: trailing whitespace
Date: Tue, 30 Dec 2014 10:26:55 -0500 [thread overview]
Message-ID: <20141230152655.GM28117@titan.lakedaemon.net> (raw)
In-Reply-To: <1419896014-13334-1-git-send-email-andreas.siegling@fau.de>
Andreas,
On Tue, Dec 30, 2014 at 12:33:34AM +0100, Andreas Siegling wrote:
> This small patch will fix the trailing whitespace in
> drivers/staging/skein/skein_generic.c.
>
> After applying the patch, there will only remain the checkpatch warning:
> WARNING: Single statement macros should not use a do {} while (0) loop
> in files which are in the directory drivers/staging/skein/
>
> Signed-off-by: Andreas Siegling <andreas.siegling@fau.de>
> Signed-off-by: Zhutao Lu <lvzhutao@gmail.com>
Why do you have have two S-o-b's?
> ---
> drivers/staging/skein/skein_generic.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/skein/skein_generic.c b/drivers/staging/skein/skein_generic.c
> index 85bd7d0..4eaae1d 100644
> --- a/drivers/staging/skein/skein_generic.c
> +++ b/drivers/staging/skein/skein_generic.c
> @@ -191,7 +191,7 @@ static int __init skein_generic_init(void)
>
> return 0;
>
> -
> +
Hmm, this extra line should just be deleted.
thx,
Jason.
> unreg512:
> crypto_unregister_shash(&alg512);
> unreg256:
> --
> 1.9.1
>
prev parent reply other threads:[~2014-12-30 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 23:33 Andreas Siegling
2014-12-30 15:26 ` Jason Cooper [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=20141230152655.GM28117@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andreas.siegling@fau.de \
--cc=devel@driverdev.osuosl.org \
--cc=devel@linuxdriverproject.org \
--cc=eric.rost@mybabylon.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lvzhutao@gmail.com \
--cc=nks@flawful.org \
--cc=trivial@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
all inboxes | Powered by JetHome®