From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH net-next v3 0/3] net: dsa: b53: Turn on Broadcom tags
Date: Sat, 11 Nov 2017 21:55:32 +0900 (KST) [thread overview]
Message-ID: <20171111.215532.671368870101325813.davem@davemloft.net> (raw)
In-Reply-To: <20171110193327.25070-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Fri, 10 Nov 2017 11:33:24 -0800
> Hi all,
>
> This was long overdue, with this patch series, the b53 driver now
> turns on Broadcom tags except for 5325 and 5365 which use an older
> format that we do not support yet (TBD).
>
> First patch is necessary in order for bgmac, used on BCM5301X and Northstar
> Plus to work correctly and successfully send ARP packets back to the requsester.
>
> Second patch is actually a bug fix, but because net/master and net-next/master
> diverge in that area, I am targeting net-next/master here.
>
> Finally, the last patch enables Broadcom tags after checking that the CPU port
> selected is either, 5, 7 or 8, since those are the only valid combinations
> given currently supported HW.
...
Series applied.
prev parent reply other threads:[~2017-11-11 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 19:33 [PATCH net-next v3 0/3] net: dsa: b53: Turn on Broadcom tags Florian Fainelli
2017-11-10 19:33 ` [PATCH net-next v3 1/3] net: bgmac: Pad packets to a minimum size Florian Fainelli
2017-11-10 20:33 ` Andrew Lunn
2017-11-10 19:33 ` [PATCH net-next v3 2/3] net: dsa: b53: Stop using dev->cpu_port incorrectly Florian Fainelli
2017-11-10 20:34 ` Andrew Lunn
2017-11-10 19:33 ` [PATCH net-next v3 3/3] net: dsa: b53: Turn on Broadcom tags Florian Fainelli
2017-11-10 20:36 ` Andrew Lunn
2017-11-11 12:55 ` 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=20171111.215532.671368870101325813.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--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).