netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: [PATCH net-next 0/3] dpaa2-eth: small updates
Date: Fri, 25 Sep 2020 17:44:18 +0300	[thread overview]
Message-ID: <20200925144421.7811-1-ioana.ciornei@nxp.com> (raw)

This patch set is just a collection of small updates to the dpaa2-eth
driver.

First, we only need to check the availability of the DTS child node, not
both child and parent node. Then remove a call to
dpaa2_eth_link_state_update() which is now just a leftover and it's not
useful in how are things working now in the PHY integration. Lastly,
modify how the driver is behaving when the the flow steering table is
used between all the traffic classes.

Ioana Ciornei (2):
  dpaa2-mac: do not check for both child and parent DTS nodes
  dpaa2-eth: no need to check link state right after ndo_open

Ionut-robert Aron (1):
  dpaa2-eth: install a single steering rule when SHARED_FS is enabled

 .../net/ethernet/freescale/dpaa2/dpaa2-eth.c  | 25 ++++++++++---------
 .../ethernet/freescale/dpaa2/dpaa2-ethtool.c  |  2 +-
 .../net/ethernet/freescale/dpaa2/dpaa2-mac.c  |  3 +--
 drivers/net/ethernet/freescale/dpaa2/dpni.h   |  4 +++
 4 files changed, 19 insertions(+), 15 deletions(-)

-- 
2.25.1


             reply	other threads:[~2020-09-25 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 14:44 Ioana Ciornei [this message]
2020-09-25 14:44 ` [PATCH net-next 1/3] dpaa2-mac: do not check for both child and parent DTS nodes Ioana Ciornei
2020-09-25 16:31   ` Andrew Lunn
2020-09-25 14:44 ` [PATCH net-next 2/3] dpaa2-eth: no need to check link state right after ndo_open Ioana Ciornei
2020-09-25 14:44 ` [PATCH net-next 3/3] dpaa2-eth: install a single steering rule when SHARED_FS is enabled Ioana Ciornei
2020-09-26  0:14 ` [PATCH net-next 0/3] dpaa2-eth: small updates David Miller

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=20200925144421.7811-1-ioana.ciornei@nxp.com \
    --to=ioana.ciornei@nxp.com \
    --cc=davem@davemloft.net \
    --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).