From: Chuck Lever <chuck.lever@oracle.com>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-rdma@vger.kernel.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH RFC] svcrdma: Ignore source port when computing DRC hash
Date: Thu, 6 Jun 2019 09:24:04 -0400 [thread overview]
Message-ID: <BD1CF3FF-887A-4204-AE3F-D48D51442E70@oracle.com> (raw)
In-Reply-To: <20190606130804.19EE32070B@mail.kernel.org>
> On Jun 6, 2019, at 9:08 AM, Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.1.7, v5.0.21, v4.19.48, v4.14.123, v4.9.180, v4.4.180.
>
> v5.1.7: Build OK!
> v5.0.21: Build OK!
> v4.19.48: Build OK!
> v4.14.123: Build OK!
> v4.9.180: Build failed! Errors:
> net/sunrpc/xprtrdma/svc_rdma_transport.c:712:2: error: implicit declaration of function ‘rpc_set_port’; did you mean ‘rpc_net_ns’? [-Werror=implicit-function-declaration]
>
> v4.4.180: Build failed! Errors:
> net/sunrpc/xprtrdma/svc_rdma_transport.c:635:2: error: implicit declaration of function ‘rpc_set_port’; did you mean ‘rpc_net_ns’? [-Werror=implicit-function-declaration]
>
>
> How should we proceed with this patch?
If the review completes without objection, I will resubmit
this patch with an updated Cc: . Thanks for testing!
--
Chuck Lever
prev parent reply other threads:[~2019-06-06 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:15 [PATCH RFC] svcrdma: Ignore source port when computing DRC hash Chuck Lever
2019-06-05 15:57 ` Olga Kornievskaia
2019-06-05 17:28 ` Chuck Lever
2019-06-06 18:13 ` Olga Kornievskaia
2019-06-06 18:33 ` Chuck Lever
2019-06-07 15:43 ` Olga Kornievskaia
2019-06-10 14:38 ` Tom Talpey
2019-06-05 16:43 ` Tom Talpey
2019-06-05 17:25 ` Chuck Lever
2019-06-10 14:50 ` Tom Talpey
2019-06-10 17:50 ` Chuck Lever
2019-06-10 19:14 ` Tom Talpey
2019-06-10 21:57 ` Chuck Lever
2019-06-10 22:13 ` Tom Talpey
2019-06-11 0:07 ` Tom Talpey
2019-06-11 14:25 ` Chuck Lever
2019-06-11 14:23 ` Chuck Lever
2019-06-06 13:08 ` Sasha Levin
2019-06-06 13:24 ` Chuck Lever [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=BD1CF3FF-887A-4204-AE3F-D48D51442E70@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).