From: Florian Fainelli <f.fainelli@gmail.com>
To: Christian Eggers <ceggers@arri.de>,
Woojung Huh <woojung.huh@microchip.com>,
Vladimir Oltean <olteanv@gmail.com>
Cc: Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: point out the tail taggers
Date: Fri, 16 Oct 2020 09:46:55 -0700 [thread overview]
Message-ID: <cb420dee-2a35-b9f9-1256-e4e3e00dd0e0@gmail.com> (raw)
In-Reply-To: <20201016162800.7696-1-ceggers@arri.de>
On 10/16/20 9:28 AM, Christian Eggers wrote:
> From a recent commit with the same summary:
>
> "The Marvell 88E6060 uses tag_trailer.c and the KSZ8795, KSZ9477 and
> KSZ9893 switches also use tail tags."
>
> Set "tail_tag" to true for KSZ8795 and KSZ9477 which were missing in the
> original commit.
>
> Fixes: 7a6ffe764be3 [net] ("net: dsa: point out the tail taggers")
> Signed-off-by: Christian Eggers <ceggers@arri.de>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2020-10-16 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 16:28 [PATCH net] net: dsa: point out the tail taggers Christian Eggers
2020-10-16 16:46 ` Florian Fainelli [this message]
2020-10-16 16:56 ` Vladimir Oltean
2020-10-16 17:25 ` kernel test robot
2020-10-16 17:25 ` kernel test robot
2020-10-16 17:33 ` Vladimir Oltean
2020-10-16 20:14 ` Andrew Lunn
2020-10-16 20:14 ` Andrew Lunn
2020-10-16 20:19 ` Vladimir Oltean
2020-10-16 21:03 ` Andrew Lunn
2020-10-16 21:03 ` Andrew Lunn
2020-10-16 21:16 ` Vladimir Oltean
2020-10-16 21:33 ` Vladimir Oltean
2020-10-16 22:56 ` Jakub Kicinski
2020-10-16 22:56 ` Jakub Kicinski
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=cb420dee-2a35-b9f9-1256-e4e3e00dd0e0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=ceggers@arri.de \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.