From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
saeedm@nvidia.com, stefan.wahren@i2se.com
Subject: Re: [PATCH net-next] net: vertexcom: default to disabled on kbuild
Date: Mon, 03 Jan 2022 10:50:09 +0000 [thread overview]
Message-ID: <164120700956.2591.9697479878144142561.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220102221126.354332-1-saeed@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 2 Jan 2022 14:11:26 -0800 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
>
> Sorry for being rude but new vendors/drivers are supposed to be disabled
> by default, otherwise we will have to manually keep track of all vendors
> we are not interested in building.
>
> Fixes: 2f207cbf0dd4 ("net: vertexcom: Add MSE102x SPI support")
> CC: Stefan Wahren <stefan.wahren@i2se.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next] net: vertexcom: default to disabled on kbuild
https://git.kernel.org/netdev/net-next/c/6bf950a8ff72
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-01-03 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 22:11 [PATCH net-next] net: vertexcom: default to disabled on kbuild Saeed Mahameed
2022-01-03 10:50 ` patchwork-bot+netdevbpf [this message]
2022-01-03 16:43 ` Jakub Kicinski
2022-01-04 8:25 ` Saeed Mahameed
2022-01-04 15:15 ` Jakub Kicinski
2022-01-04 8:57 ` Leon Romanovsky
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=164120700956.2591.9697479878144142561.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=stefan.wahren@i2se.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.