From: Andrew Lunn <andrew@lunn.ch>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next] net: dsa: add CONFIG_NET_DSA_LEGACY
Date: Thu, 21 Jul 2016 16:52:42 +0200 [thread overview]
Message-ID: <20160721145242.GP11309@lunn.ch> (raw)
In-Reply-To: <87zipbm4kf.fsf@ketchup.mtl.sfl>
On Thu, Jul 21, 2016 at 10:46:56AM -0400, Vivien Didelot wrote:
> Florian Fainelli <f.fainelli@gmail.com> writes:
>
> > Le 20/07/2016 à 17:35, Andrew Lunn a écrit :
> >> On Wed, Jul 20, 2016 at 06:26:41PM -0400, Vivien Didelot wrote:
> >>> This patch simply moves the legacy DSA code from dsa.c to legacy.c,
> >>> except the few shared symbols which remain in dsa.c.
> >>
> >> I think it is a bit early for this. Lets convert all in kernel users
> >> to the new binding first.
> >
> > Fine with me, let's try to get the in-tree DTS files converted to the
> > new binding by v4.9 so we can then introduce this Kconfig symbol and
> > start producing warnings if the old binding is encountered, how does
> > that sound?
>
> If you guys prefer going that way, that's fine with me too ;-)
Yes, i would prefer that.
Andrew
next prev parent reply other threads:[~2016-07-21 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 22:26 [PATCH net-next] net: dsa: add CONFIG_NET_DSA_LEGACY Vivien Didelot
2016-07-21 0:35 ` Andrew Lunn
2016-07-21 2:15 ` Florian Fainelli
2016-07-21 14:46 ` Vivien Didelot
2016-07-21 14:52 ` Andrew Lunn [this message]
2016-07-21 14:44 ` Vivien Didelot
-- strict thread matches above, loose matches on Subject: below --
2017-04-11 20:52 Vivien Didelot
2017-04-11 20:59 ` Florian Fainelli
2017-04-12 14:22 ` Vivien Didelot
2017-04-11 21:20 ` Andrew Lunn
2017-04-12 14:50 ` Vivien Didelot
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=20160721145242.GP11309@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).