From: David Miller <davem@davemloft.net>
To: damien.thebault@vitec.com
Cc: vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
andrew@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net: dsa: b53: Add BCM5389 support
Date: Fri, 01 Jun 2018 11:16:02 -0400 (EDT) [thread overview]
Message-ID: <20180601.111602.1400866592970592477.davem@davemloft.net> (raw)
In-Reply-To: <1ce940f7dc9c2d57c53e93341629e1981755689a.camel@vitec.com>
From: Damien Thébault <damien.thebault@vitec.com>
Date: Thu, 31 May 2018 07:04:01 +0000
> This patch adds support for the BCM5389 switch connected through MDIO.
>
> Signed-off-by: Damien Thébault <damien.thebault@vitec.com>
Applied, thank you.
prev parent reply other threads:[~2018-06-01 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 7:04 [PATCH v2] net: dsa: b53: Add BCM5389 support Damien Thébault
2018-05-31 14:14 ` Florian Fainelli
2018-06-01 15:16 ` 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=20180601.111602.1400866592970592477.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=damien.thebault@vitec.com \
--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).