From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com, john@phrozen.org
Subject: Re: [PATCH net-next v4 0/4] net: dsa: Multi-CPU ground work (v4)
Date: Tue, 13 Jun 2017 16:35:42 -0400 (EDT) [thread overview]
Message-ID: <20170613.163542.1408709625950662812.davem@davemloft.net> (raw)
In-Reply-To: <20170613202722.17598-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Tue, 13 Jun 2017 13:27:18 -0700
> This patch series prepares the ground for adding mutliple CPU port support to
> DSA, and starts by removing redundant pieces of information such as
> master_netdev which is cpu_dp->ethernet. Finally drivers are moved away from
> directly accessing ds->dst->cpu_dp and use appropriate helper functions.
>
> Note that if you have Device Tree blobs/platform configurations that are
> currently listing multiple CPU ports, the proposed behavior in
> dsa_ds_get_cpu_dp() will be to return the last bit set in ds->cpu_port_mask.
>
> Future plans include:
> - making dst->cpu_dp a flexible data structure (array, list, you name it)
> - having the ability for drivers to return a default/preferred CPU port (if
> necessary)
>
> Changes in v4:
>
> - fixed build warning with NETPOLL enabled
...
Applied, thanks for the quick respin.
prev parent reply other threads:[~2017-06-13 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 20:27 [PATCH net-next v4 0/4] net: dsa: Multi-CPU ground work (v4) Florian Fainelli
2017-06-13 20:27 ` [PATCH v4 1/4] net: dsa: Remove master_netdev and use dst->cpu_dp->netdev Florian Fainelli
2017-06-13 20:27 ` [PATCH v4 2/4] net: dsa: Relocate master ethtool operations Florian Fainelli
2017-06-13 20:27 ` [PATCH v4 3/4] net: dsa: Associate slave network device with CPU port Florian Fainelli
2017-06-13 20:27 ` [PATCH v4 4/4] net: dsa: Introduce dsa_get_cpu_port() Florian Fainelli
2017-06-13 20:35 ` David Miller [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=20170613.163542.1408709625950662812.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=john@phrozen.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).