From: patchwork-bot+netdevbpf@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: davem@davemloft.net, kbusch@kernel.org, axboe@fb.com, hch@lst.de,
sagi@grimberg.me, okulkarni@marvell.com, hare@suse.de,
dbalandin@marvell.com, himanshu.madhani@oracle.com,
smalin@marvell.com, pmladek@suse.com,
linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m
Date: Tue, 08 Jun 2021 19:10:05 +0000 [thread overview]
Message-ID: <162317940597.2276.17237091802998795532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <39b1a3684880e1d85ef76e34403886e8f1d22508.1623149635.git.geert+renesas@glider.be>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 8 Jun 2021 12:56:09 +0200 you wrote:
> The help text for the symbol controlling support for the NVM Express
> over Fabrics TCP offload common layer suggests to not enable this
> support when unsure.
>
> Hence drop the "default m", which actually means "default y" if
> CONFIG_MODULES is not enabled.
>
> [...]
Here is the summary with links:
- nvme: NVME_TCP_OFFLOAD should not default to m
https://git.kernel.org/netdev/net-next/c/762411542050
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:[~2021-06-08 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 10:56 [PATCH] nvme: NVME_TCP_OFFLOAD should not default to m Geert Uytterhoeven
2021-06-08 12:19 ` Christoph Hellwig
2021-06-08 13:37 ` Geert Uytterhoeven
2021-06-08 13:43 ` please drop the nvme code from net-next Christoph Hellwig
2021-06-08 19:08 ` David Miller
2021-06-08 19:40 ` Keith Busch
2021-06-08 19:10 ` 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=162317940597.2276.17237091802998795532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=axboe@fb.com \
--cc=davem@davemloft.net \
--cc=dbalandin@marvell.com \
--cc=geert+renesas@glider.be \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=himanshu.madhani@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=okulkarni@marvell.com \
--cc=pmladek@suse.com \
--cc=sagi@grimberg.me \
--cc=smalin@marvell.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 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).