From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, Dave Jones <davej@codemonkey.org.uk>,
Steve Douthit <stephend@silicom-usa.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH] ixgbe: fix Kconfig when driver is not a module
Date: Thu, 03 Jan 2019 13:42:20 -0800 [thread overview]
Message-ID: <b3f82b0bfb338ab011049795d6c704a29e97bcf5.camel@intel.com> (raw)
In-Reply-To: <20190103213519.9754-1-jeffrey.t.kirsher@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
On Thu, 2019-01-03 at 13:35 -0800, Jeff Kirsher wrote:
> The new ability added to the driver to use mii_bus to handle MII
> related
> ioctls is causing compile issues when the driver is compiled into the
> kernel (i.e. not a module).
>
> The simple solution of requiring the driver to be compiled as a
> module when
> MDIO_BUS is a module, causes a recursion Kconfig issue due to IPSec
> dependencies.
>
> So created another Kconfig option for ixgbe, to enable mdio_bus
> support for
> DSA devices. This solution solves the problem when the ixgbe driver
> is
> compiled into the kernel and MDIO_BUS is compiled as a module. In
> this
> case, the IXGBE_MDIO option is disabled and the code is not compiled
> into the driver.
>
> CC: Dave Jones <davej@codemonkey.org.uk>
> CC: Steve Douthit <stephend@silicom-usa.com>
> CC: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
> drivers/net/ethernet/intel/Kconfig | 11 ++++++++++-
> drivers/net/ethernet/intel/ixgbe/ixgbe.h | 4 ++++
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 12 ++++++++++--
> drivers/net/ethernet/intel/ixgbe/ixgbe_phy.c | 4 ++++
> drivers/net/ethernet/intel/ixgbe/ixgbe_phy.h | 3 ++-
> 5 files changed, 30 insertions(+), 4 deletions(-)
I have done the following compile tests to comfirm this resolves the
issue:
Kconfig: 1 2 3 4
-------- --- --- --- ---
ixgbe m m y y
ixgbe_mdio y n y y
mdio_bus m m m y
phylib m m m y
Test #3 resulted in ixgbe_mdio being disabled and code not compiled
into the driver.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-03 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 21:35 [PATCH] ixgbe: fix Kconfig when driver is not a module Jeff Kirsher
2019-01-03 21:42 ` Jeff Kirsher [this message]
2019-01-03 23:57 ` [Intel-wired-lan] " Bowers, AndrewX
2019-01-04 0:00 ` Steve Douthit
2019-01-04 0:55 ` Jeff Kirsher
2019-01-04 15:09 ` Steve Douthit
2019-01-04 18:06 ` Jeff Kirsher
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=b3f82b0bfb338ab011049795d6c704a29e97bcf5.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davej@codemonkey.org.uk \
--cc=f.fainelli@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=stephend@silicom-usa.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