All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Joe Hershberger <joe.hershberger@ni.com>,
	Ramon Fried <rfried.dev@gmail.com>,
	 Ryan Chen <ryan_chen@aspeedtech.com>,
	BMC-SW@aspeedtech.com
Cc: "Cédric Le Goater" <clg@kaod.org>,
	"Samuel Mendoza-Jonas" <sam@mendozajonas.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v4 0/4] net: Enable NC-SI support
Date: Thu, 15 Sep 2022 01:11:54 +0000	[thread overview]
Message-ID: <CACPK8XcbU5AmFHjokJPKafMB9HD=Bw+O+qg1VnB7JjtMEeDg+w@mail.gmail.com> (raw)
In-Reply-To: <CACPK8Xc9YNOvBqwA6=XZu7Zq6Ab1DzmT3WzKVr2q8ZyXEAvVpQ@mail.gmail.com>

On Tue, 23 Aug 2022 at 04:54, Joel Stanley <joel@jms.id.au> wrote:
>
> On Mon, 8 Aug 2022 at 12:16, Joel Stanley <joel@jms.id.au> wrote:
> >
> > Back in 2019 Sam submitted NC-SI support. The NC-SI PHY driver was
> > merged (patches 1 and 2), but we never got around to merging patches 3
> > and 4:
> >
> >  https://lore.kernel.org/u-boot/20190618013720.2823-1-sam@mendozajonas.com/
> >
> > Sam as long since moved on from working on the Aspeed BMCs, but the code
> > has been in use in the vendor fork for some time.
> >
> > This refreshes his patches and enables support in the Aspeed defconfigs,
> > giving compile coverage to the NC-SI phy.
> >
> > v4 splits the ncsi integration and cmd code into separate patches, and
> > adds r-b from Ramon and Cédric to patches 3 and 4.
>
> We have review on these patches now. Can we get them merged?

ping

>
> >
> > Joel Stanley (1):
> >   config/aspeed: Enable NC-SI support
> >
> > Samuel Mendoza-Jonas (3):
> >   net: NC-SI setup and handling
> >   cmd: Add ncsi command
> >   net/ftgmac100: Add NC-SI mode support
> >
> >  include/net.h                 |  2 +-
> >  include/phy.h                 |  2 ++
> >  cmd/net.c                     | 22 ++++++++++++++++++++++
> >  drivers/net/ftgmac100.c       | 14 ++++++++++----
> >  drivers/net/phy/ncsi.c        |  1 +
> >  drivers/net/phy/phy.c         |  9 ++++++++-
> >  net/net.c                     | 27 ++++++++++++++++++++++++++-
> >  cmd/Kconfig                   |  8 ++++++++
> >  configs/evb-ast2500_defconfig |  2 ++
> >  configs/evb-ast2600_defconfig |  2 ++
> >  10 files changed, 82 insertions(+), 7 deletions(-)
> >
> > --
> > 2.35.1
> >

  reply	other threads:[~2022-09-15  1:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 12:16 [PATCH v4 0/4] net: Enable NC-SI support Joel Stanley
2022-08-08 12:16 ` [PATCH v4 1/4] net: NC-SI setup and handling Joel Stanley
2022-08-08 12:57   ` Cédric Le Goater
2022-08-08 18:42   ` Ramon Fried
2022-10-24 12:21   ` Tom Rini
2022-08-08 12:16 ` [PATCH v4 2/4] cmd: Add ncsi command Joel Stanley
2022-08-08 12:56   ` Cédric Le Goater
2022-10-24 12:21   ` Tom Rini
2022-08-08 12:16 ` [PATCH v4 3/4] net/ftgmac100: Add NC-SI mode support Joel Stanley
2022-10-24 12:21   ` Tom Rini
2022-08-08 12:16 ` [PATCH v4 4/4] config/aspeed: Enable NC-SI support Joel Stanley
2022-10-24 12:21   ` Tom Rini
2022-08-23  4:54 ` [PATCH v4 0/4] net: " Joel Stanley
2022-09-15  1:11   ` Joel Stanley [this message]
2022-10-18 23:56     ` Joel Stanley

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='CACPK8XcbU5AmFHjokJPKafMB9HD=Bw+O+qg1VnB7JjtMEeDg+w@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=BMC-SW@aspeedtech.com \
    --cc=clg@kaod.org \
    --cc=joe.hershberger@ni.com \
    --cc=rfried.dev@gmail.com \
    --cc=ryan_chen@aspeedtech.com \
    --cc=sam@mendozajonas.com \
    --cc=u-boot@lists.denx.de \
    /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.