From: David Miller <davem@davemloft.net>
To: florinel.iordache@nxp.com
Cc: netdev@vger.kernel.org, madalin.bucur@nxp.com,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next] fsl/fman: implement several errata workarounds
Date: Fri, 11 Aug 2017 14:37:55 -0700 (PDT) [thread overview]
Message-ID: <20170811.143755.1486109421287401840.davem@davemloft.net> (raw)
In-Reply-To: <1502372824-30180-1-git-send-email-florinel.iordache@nxp.com>
From: Florinel Iordache <florinel.iordache@nxp.com>
Date: Thu, 10 Aug 2017 16:47:04 +0300
> Implemented workarounds for the following dTSEC Erratum:
> A002, A004, A0012, A0014, A004839 on several operations
> that involve MAC CFG register changes: adjust link,
> rx pause frames, modify MAC address.
>
> Signed-off-by: Florinel Iordache <florinel.iordache@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2017-08-11 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 13:47 [PATCH net-next] fsl/fman: implement several errata workarounds Florinel Iordache
2017-08-11 8:41 ` Madalin-cristian Bucur
2017-08-11 21:37 ` 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=20170811.143755.1486109421287401840.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=florinel.iordache@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
/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).