From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?H=C3=A5kon_Bugge_=3Chaakon=2Ebugge=40oracle=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: allison.henderson@oracle.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, stable@vger.kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4] rds: ib: Remove unused extern definition
Date: Tue, 09 Sep 2025 01:30:38 +0000 [thread overview]
Message-ID: <175738143824.108077.16911055038125503100.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250905101958.4028647-1-haakon.bugge@oracle.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 5 Sep 2025 12:19:57 +0200 you wrote:
> In the old days, RDS used FMR (Fast Memory Registration) to register
> IB MRs to be used by RDMA. A newer and better verbs based
> registration/de-registration method called FRWR (Fast Registration
> Work Request) was added to RDS by commit 1659185fb4d0 ("RDS: IB:
> Support Fastreg MR (FRMR) memory registration mode") in 2016.
>
> Detection and enablement of FRWR was done in commit 2cb2912d6563
> ("RDS: IB: add Fastreg MR (FRMR) detection support"). But said commit
> added an extern bool prefer_frmr, which was not used by said commit -
> nor used by later commits. Hence, remove it.
>
> [...]
Here is the summary with links:
- [net-next,v4] rds: ib: Remove unused extern definition
https://git.kernel.org/netdev/net-next/c/9f0730b063b4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-09 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 10:19 [PATCH net-next v4] rds: ib: Remove unused extern definition Håkon Bugge
2025-09-09 1:30 ` patchwork-bot+netdevbpf [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=175738143824.108077.16911055038125503100.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?H=C3=A5kon_Bugge_=3Chaakon=2Ebugge=40oracle=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=allison.henderson@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--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