From: Andrew Lunn <andrew@lunn.ch>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH net-next 08/15] dsa: Keep link list of tag drivers
Date: Thu, 18 Apr 2019 15:19:47 +0200 [thread overview]
Message-ID: <20190418131947.GB542@lunn.ch> (raw)
In-Reply-To: <19b64e9a-90ce-0645-f3ab-c096b5859258@cogentembedded.com>
On Thu, Apr 18, 2019 at 12:35:44PM +0300, Sergei Shtylyov wrote:
> On 18.04.2019 5:31, Andrew Lunn wrote:
>
> >Let the tag drivers register themselves with the DSA core, keeping
> >them in a linked list.
> >
> >Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> >---
> > include/net/dsa.h | 2 ++
> > net/dsa/dsa.c | 35 ++++++++++++++++++++++++++++++++++-
> > 2 files changed, 36 insertions(+), 1 deletion(-)
> >
> [...]
> >diff --git a/net/dsa/dsa.c b/net/dsa/dsa.c
> >index a49e230b6247..861fe1441a7d 100644
> >--- a/net/dsa/dsa.c
> >+++ b/net/dsa/dsa.c
> >@@ -27,6 +27,9 @@
> [...]
> > int dsa_tag_drivers_register(struct dsa_device_ops *ops[],
> > unsigned int count, struct module *owner)
> > {
> >- return 0;
> >+ int err, i;
> >+
> >+ for (i = 0; i < count; i++) {
> >+ err = dsa_tag_driver_register(ops[i], owner);
> >+ if (err)
> >+ break;
> >+ }
> >+
> >+ return err;
>
> What if count == 0? Can't happen?
Hi Sergei
The current drivers would prevent that. But to be robust, i will add a
check.
Thanks
Andrew
next prev parent reply other threads:[~2019-04-18 13:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 2:31 [PATCH net-next 00/15] Make DSA tag drivers kernel modules Andrew Lunn
2019-04-18 2:31 ` [PATCH net-next 01/15] dsa: Add SPDX header to tag drivers Andrew Lunn
2019-04-18 17:35 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 02/15] dsa: Move tagger name into its ops structure Andrew Lunn
2019-04-18 17:37 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 03/15] dsa: Add MODULE_ALIAS to taggers in preperation to become modules Andrew Lunn
2019-04-19 15:25 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 04/15] dsa: Add MODULE_LICENSE to tag drivers Andrew Lunn
2019-04-18 17:51 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 05/15] dsa: Add TAG protocol to tag ops Andrew Lunn
2019-04-19 15:27 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 06/15] dsa: Remove const from tag driver ops structure Andrew Lunn
2019-04-18 17:58 ` Florian Fainelli
2019-04-18 21:47 ` Andrew Lunn
2019-04-19 15:26 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 07/15] dsa: Add boilerplate helper to register DSA tag driver modules Andrew Lunn
2019-04-19 15:29 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 08/15] dsa: Keep link list of tag drivers Andrew Lunn
2019-04-18 7:25 ` David Miller
2019-04-18 9:35 ` Sergei Shtylyov
2019-04-18 13:19 ` Andrew Lunn [this message]
2019-04-18 14:40 ` Sergei Shtylyov
2019-04-19 15:30 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 09/15] dsa: Register the none tagger ops Andrew Lunn
2019-04-19 15:31 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 10/15] dsa: Rename dsa_resolve_tag_protocol() to _get ready for locking Andrew Lunn
2019-04-19 15:31 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 11/15] dsa: Add stub tag driver put method Andrew Lunn
2019-04-19 15:32 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 12/15] dsa: Make use of the list of tag drivers Andrew Lunn
2019-04-19 15:33 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 13/15] dsa: Cleanup unneeded table and make tag structures static Andrew Lunn
2019-04-19 15:34 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 14/15] dsa: Allow tag drivers to be built as modules Andrew Lunn
2019-04-19 15:38 ` Florian Fainelli
2019-04-18 2:31 ` [PATCH net-next 15/15] dsa: tag_brcm: Avoid unused symbols Andrew Lunn
2019-04-19 15:39 ` Florian Fainelli
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=20190418131947.GB542@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vivien.didelot@gmail.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).