From: Simon Horman <simon.horman@corigine.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Dimitris Michailidis <dmichail@fungible.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
oss-drivers@corigine.com,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: remove redundant config PCI dependency for some network driver configs
Date: Wed, 11 Jan 2023 14:16:40 +0100 [thread overview]
Message-ID: <Y762uPnsRuwKi4is@corigine.com> (raw)
In-Reply-To: <20230111125855.19020-1-lukas.bulwahn@gmail.com>
On Wed, Jan 11, 2023 at 01:58:55PM +0100, Lukas Bulwahn wrote:
> [Some people who received this message don't often get email from lukas.bulwahn@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> While reviewing dependencies in some Kconfig files, I noticed the redundant
> dependency "depends on PCI && PCI_MSI". The config PCI_MSI has always,
> since its introduction, been dependent on the config PCI. So, it is
> sufficient to just depend on PCI_MSI, and know that the dependency on PCI
> is implicitly implied.
>
> Reduce the dependencies of some network driver configs.
> No functional change and effective change of Kconfig dependendencies.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> drivers/net/ethernet/freescale/enetc/Kconfig | 4 ++--
> drivers/net/ethernet/fungible/funeth/Kconfig | 2 +-
> drivers/net/ethernet/netronome/Kconfig | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
For nfp portion.
Acked-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-01-11 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 12:58 [PATCH] net: remove redundant config PCI dependency for some network driver configs Lukas Bulwahn
2023-01-11 13:16 ` Simon Horman [this message]
2023-01-11 17:38 ` Dimitris Michailidis
2023-01-13 19:38 ` Jakub Kicinski
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=Y762uPnsRuwKi4is@corigine.com \
--to=simon.horman@corigine.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=dmichail@fungible.com \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.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).