From: Steffen Klassert <steffen.klassert@secunet.com>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] padata: Remove unused but set variables
Date: Fri, 21 Oct 2016 11:00:47 +0200 [thread overview]
Message-ID: <20161021090047.GO19080@gauss.secunet.com> (raw)
In-Reply-To: <20161017101608.18007-1-tklauser@distanz.ch>
On Mon, Oct 17, 2016 at 12:16:08PM +0200, Tobias Klauser wrote:
> Remove the unused but set variable pinst in padata_parallel_worker to
> fix the following warning when building with 'W=1':
>
> kernel/padata.c: In function ‘padata_parallel_worker’:
> kernel/padata.c:68:26: warning: variable ‘pinst’ set but not used [-Wunused-but-set-variable]
>
> Also remove the now unused variable pd which is only used to set pinst.
>
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
Thanks!
next prev parent reply other threads:[~2016-10-21 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 10:16 [PATCH] padata: Remove unused but set variables Tobias Klauser
2016-10-21 9:00 ` Steffen Klassert [this message]
2016-10-25 3:38 ` Herbert Xu
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=20161021090047.GO19080@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tklauser@distanz.ch \
/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