netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Mathieu Olivari <mathieu@codeaurora.org>,
	davem@davemloft.net, f.fainelli@gmail.com, linux@roeck-us.net,
	jiri@resnulli.us, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: dsa: make NET_DSA manually selectable from the config
Date: Sun, 22 Mar 2015 20:58:32 +0300	[thread overview]
Message-ID: <550F02C8.40809@cogentembedded.com> (raw)
In-Reply-To: <1426901463-31913-1-git-send-email-mathieu@codeaurora.org>

Hello.

On 3/21/2015 4:31 AM, Mathieu Olivari wrote:

> Change bd76a116707bd2381da36cf7c3183df11293f1d6 made all DSA drivers

    s/Change/Commit/, perhaps?
    And please also specify that commit's summary line in parens.

> depend on NET_DSA rather than selecting them. However, as the only way
> to select this option was to actually select a driver, it made DSA
> impossible to enable at all.

> This patch adds an explicit entry which the user will have to enable
> prior selecting a driver.

> Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>
> ---
>   net/dsa/Kconfig | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)

> diff --git a/net/dsa/Kconfig b/net/dsa/Kconfig
> index 087e654..4f3cce1 100644
> --- a/net/dsa/Kconfig
> +++ b/net/dsa/Kconfig
> @@ -5,9 +5,12 @@ config HAVE_NET_DSA
>   # Drivers must select NET_DSA and the appropriate tagging format
>
>   config NET_DSA
> -	tristate
> +	tristate "Distributed Switch Architecture"
>   	depends on HAVE_NET_DSA && NET_SWITCHDEV
>   	select PHYLIB
> +	---help---

    Hm, why not just help?

WBR, Sergei

      parent reply	other threads:[~2015-03-22 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21  1:31 [PATCH] net: dsa: make NET_DSA manually selectable from the config Mathieu Olivari
2015-03-21  1:37 ` Guenter Roeck
2015-03-21  1:39 ` David Miller
2015-03-21 15:21 ` Andrew Lunn
2015-03-22 17:58 ` Sergei Shtylyov [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=550F02C8.40809@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mathieu@codeaurora.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;
as well as URLs for NNTP newsgroup(s).