From: Neil Armstrong <narmstrong@baylibre.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
vivien.didelot@savoirfairelinux.com,
Fabian Frederick <fabf@skynet.be>,
Pavel Nakonechny <pavel.nakonechny@skitlab.ru>,
Joe Perches <joe@perches.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/5] net: dsa: cleanup dsa driver
Date: Mon, 7 Dec 2015 11:25:57 +0100 [thread overview]
Message-ID: <56655EB5.6080600@baylibre.com> (raw)
In-Reply-To: <56323100.9000304@baylibre.com>
On 10/29/2015 03:45 PM, Neil Armstrong wrote:
> Introduce a new remove callback to allow DSA drivers to cleanup their
> ressources.
> Then add a remove implementation for bcm_sf2 and mv88e6xxx.
>
> This patch was not tested due of a lack of hardware.
>
> v2: add remove callback patch to the serie
> v3: separate & fix ppu remove callback into a proper patch
>
> Neil Armstrong (5):
> net: dsa: allow switch drivers to cleanup their resources
> net: dsa: bcm_sf2: cleanup resources in remove callback
> net: dsa: mv88e6xxx: add common remove function
> net: dsa: make usage of mv88e6xxx common remove function
> net: dsa: add mv88e6xxx ppu remove function for mv88e6131
>
> drivers/net/dsa/bcm_sf2.c | 20 ++++++++++++++++++++
> drivers/net/dsa/mv88e6123_61_65.c | 1 +
> drivers/net/dsa/mv88e6131.c | 8 ++++++++
> drivers/net/dsa/mv88e6171.c | 1 +
> drivers/net/dsa/mv88e6352.c | 1 +
> drivers/net/dsa/mv88e6xxx.c | 18 ++++++++++++++++++
> drivers/net/dsa/mv88e6xxx.h | 2 ++
> include/net/dsa.h | 1 +
> net/dsa/dsa.c | 4 ++++
> 9 files changed, 56 insertions(+)
>
Hi All,
Did someone had a chance to test this ?
Having such code will help for the final DSA reworking.
Neil
prev parent reply other threads:[~2015-12-07 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 14:45 [RFC PATCH v3 0/5] net: dsa: cleanup dsa driver Neil Armstrong
2015-12-07 10:25 ` Neil Armstrong [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=56655EB5.6080600@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fabf@skynet.be \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=pavel.nakonechny@skitlab.ru \
--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