From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: YueHaibing <yuehaibing@huawei.com>,
David Howells <dhowells@redhat.com>,
davem@davemloft.net
Cc: linux-afs@lists.infradead.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] rxrpc: use correct kvec num while send response packet in rxrpc_reject_packets
Date: Tue, 9 Oct 2018 18:34:03 +0300 [thread overview]
Message-ID: <365d2f43-089a-1246-d354-2b3481d50b9a@cogentembedded.com> (raw)
In-Reply-To: <1539094525-174123-1-git-send-email-yuehaibing@huawei.com>
On 10/09/2018 05:15 PM, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> net/rxrpc/output.c: In function 'rxrpc_reject_packets':
> net/rxrpc/output.c:527:11: warning:
> variable 'ioc' set but not used [-Wunused-but-set-variable]
>
> 'ioc' is the correct kvec num while send response packet.
>
> Fixes: commit ece64fec164f ("rxrpc: Emit BUSY packets when supposed to rather than
ABORTs")
"commit" not needed here.
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
[...]
MBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: YueHaibing <yuehaibing@huawei.com>,
David Howells <dhowells@redhat.com>,
davem@davemloft.net
Cc: linux-afs@lists.infradead.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] rxrpc: use correct kvec num while send response packet in rxrpc_reject_packets
Date: Tue, 09 Oct 2018 15:34:03 +0000 [thread overview]
Message-ID: <365d2f43-089a-1246-d354-2b3481d50b9a@cogentembedded.com> (raw)
In-Reply-To: <1539094525-174123-1-git-send-email-yuehaibing@huawei.com>
On 10/09/2018 05:15 PM, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> net/rxrpc/output.c: In function 'rxrpc_reject_packets':
> net/rxrpc/output.c:527:11: warning:
> variable 'ioc' set but not used [-Wunused-but-set-variable]
>
> 'ioc' is the correct kvec num while send response packet.
>
> Fixes: commit ece64fec164f ("rxrpc: Emit BUSY packets when supposed to rather than
ABORTs")
"commit" not needed here.
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2018-10-09 22:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 2:31 [PATCH net-next] rxrpc: Remove set but not used variable 'ioc' YueHaibing
2018-10-09 2:31 ` YueHaibing
2018-10-09 10:13 ` David Howells
2018-10-09 10:13 ` David Howells
2018-10-09 12:04 ` YueHaibing
2018-10-09 12:04 ` YueHaibing
2018-10-11 8:38 ` Dan Carpenter
2018-10-11 8:38 ` Dan Carpenter
2018-10-11 20:38 ` David Howells
2018-10-11 20:38 ` David Howells
2018-10-09 14:15 ` [PATCH v2] rxrpc: use correct kvec num while send response packet in rxrpc_reject_packets YueHaibing
2018-10-09 14:15 ` YueHaibing
2018-10-09 15:34 ` Sergei Shtylyov [this message]
2018-10-09 15:34 ` Sergei Shtylyov
2018-10-10 1:19 ` YueHaibing
2018-10-10 1:19 ` YueHaibing
2018-10-10 1:55 ` [PATCH v3] " YueHaibing
2018-10-10 2:06 ` YueHaibing
-- strict thread matches above, loose matches on Subject: below --
2018-08-02 3:36 [PATCH net-next] rxrpc: Remove set but not used variable 'nowj' Wei Yongjun
2018-08-02 3:36 ` Wei Yongjun
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=365d2f43-089a-1246-d354-2b3481d50b9a@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=yuehaibing@huawei.com \
/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.