From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next 0/5] net: dsa: loop: Preparatory changes for
Date: Mon, 3 Aug 2020 22:33:57 +0200 [thread overview]
Message-ID: <20200803203357.GE1919070@lunn.ch> (raw)
In-Reply-To: <20200803200354.45062-1-f.fainelli@gmail.com>
On Mon, Aug 03, 2020 at 01:03:49PM -0700, Florian Fainelli wrote:
> Hi David,
>
> These patches are all meant to help pave the way for a 802.1Q data path
> added to the mockup driver, making it more useful than just testing for
> configuration.
Could you give some more details. I assume the tag driver is going be
to more active. At least, that would make sense with the data
structure moves.
Andrew
next prev parent reply other threads:[~2020-08-03 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 20:03 [PATCH net-next 0/5] net: dsa: loop: Preparatory changes for Florian Fainelli
2020-08-03 20:03 ` [PATCH net-next 1/5] net: dsa: loop: PVID should be per-port Florian Fainelli
2020-08-03 20:34 ` Andrew Lunn
2020-08-03 20:03 ` [PATCH net-next 2/5] net: dsa: loop: Support 4K VLANs Florian Fainelli
2020-08-03 20:27 ` Andrew Lunn
2020-08-03 20:29 ` Florian Fainelli
2020-08-03 20:03 ` [PATCH net-next 3/5] net: dsa: loop: Move data structures to header Florian Fainelli
2020-08-03 20:03 ` [PATCH net-next 4/5] net: dsa: loop: Wire-up MTU callbacks Florian Fainelli
2020-08-03 20:29 ` Andrew Lunn
2020-08-03 20:03 ` [PATCH net-next 5/5] net: dsa: loop: Set correct number of ports Florian Fainelli
2020-08-03 20:29 ` Andrew Lunn
2020-08-03 20:33 ` Andrew Lunn [this message]
2020-08-03 20:36 ` [PATCH net-next 0/5] net: dsa: loop: Preparatory changes for Florian Fainelli
2020-08-04 1:20 ` David Miller
2020-08-04 2:22 ` 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=20200803203357.GE1919070@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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).