public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Claudiu Manoil <claudiu.manoil@nxp.com>
Cc: David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexandru Marginean <alexandru.marginean@nxp.com>,
	Catalin Horghidan <catalin.horghidan@nxp.com>
Subject: Re: [PATCH net-next v2 1/4] enetc: Introduce basic PF and VF ENETC ethernet drivers
Date: Thu, 22 Nov 2018 19:05:57 +0100	[thread overview]
Message-ID: <20181122180557.GC10697@lunn.ch> (raw)
In-Reply-To: <VI1PR04MB48803D4A3D8D331046CFC63196DB0@VI1PR04MB4880.eurprd04.prod.outlook.com>

On Thu, Nov 22, 2018 at 01:06:01PM +0000, Claudiu Manoil wrote:
> >-----Original Message-----
> >From: David Miller <davem@davemloft.net>
> >Sent: Thursday, November 22, 2018 2:21 AM
> >To: Claudiu Manoil <claudiu.manoil@nxp.com>
> >Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Alexandru
> >Marginean <alexandru.marginean@nxp.com>; Catalin Horghidan
> ><catalin.horghidan@nxp.com>
> >Subject: Re: [PATCH net-next v2 1/4] enetc: Introduce basic PF and VF ENETC
> >ethernet drivers
> >
> >From: Claudiu Manoil <claudiu.manoil@nxp.com>
> >Date: Tue, 20 Nov 2018 20:15:31 +0200
> >
> >> diff --git a/drivers/net/ethernet/freescale/Makefile
> >b/drivers/net/ethernet/freescale/Makefile
> >> index 3b4ff08..20e5c2f9 100644
> >> --- a/drivers/net/ethernet/freescale/Makefile
> >> +++ b/drivers/net/ethernet/freescale/Makefile
> >> @@ -23,3 +23,4 @@ obj-$(CONFIG_FSL_FMAN) += fman/
> >>  obj-$(CONFIG_FSL_DPAA_ETH) += dpaa/
> >>
> >>  obj-$(CONFIG_FSL_DPAA2_ETH) += dpaa2/
> >> +obj-$(CONFIG_NET_VENDOR_FREESCALE) += enetc/
> >
> >The driver enable Kconfig option should guard traversing into the
> >driver subdirectory, not the vendor enable Kconfig knob.
> 
> The enetc/ dir contains 2 drivers, that share a lot of common code.
> Would you agree if I change the vendor enable with the two configs
> (one for each driver) as below?
> 
> -obj-$(CONFIG_NET_VENDOR_FREESCALE) += enetc/
> +obj-$(CONFIG_FSL_ENETC) += enetc/
> +obj-$(CONFIG_FSL_ENETC_VF) += enetc/

CONFIG_NET_VENDOR_FREESCALE should hide/show all Freescale drivers.

Once you show all Freescale drivers, there should be an option to
enable each individual driver.

Does the ENETC_VF driver depend on the ENETC driver? If so, when
CONFIG_FSL_ENETC is enabled, the CONFIG_FSL_ENETC_VF should be
unhidden.

	Andrew

  reply	other threads:[~2018-11-22 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 18:15 [PATCH net-next v2 0/4] Introduce ENETC ethernet drivers Claudiu Manoil
2018-11-20 18:15 ` [PATCH net-next v2 1/4] enetc: Introduce basic PF and VF " Claudiu Manoil
2018-11-22  0:21   ` David Miller
2018-11-22 13:06     ` Claudiu Manoil
2018-11-22 18:05       ` Andrew Lunn [this message]
2018-11-23 10:35         ` Claudiu Manoil
2018-11-20 18:15 ` [PATCH net-next v2 2/4] enetc: Add ethtool statistics Claudiu Manoil
2018-11-20 18:15 ` [PATCH net-next v2 3/4] enetc: Add vf to pf messaging support Claudiu Manoil
2018-11-20 18:15 ` [PATCH net-next v2 4/4] enetc: Add RFS and RSS support Claudiu Manoil

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=20181122180557.GC10697@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alexandru.marginean@nxp.com \
    --cc=catalin.horghidan@nxp.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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