All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 0/6] staging: dpaa2-ethsw: cleanup of link state and MAC addresses
Date: Wed, 15 Jul 2020 16:10:18 +0200	[thread overview]
Message-ID: <20200715141018.GA3377845@kroah.com> (raw)
In-Reply-To: <20200714133431.17532-1-ioana.ciornei@nxp.com>

On Tue, Jul 14, 2020 at 04:34:25PM +0300, Ioana Ciornei wrote:
> This patch set is cleaning up the link state handling of the switch
> ports in patches 1-4. The last two patches are setting up the MAC
> addresses of the switch ports automatically so that the user is not
> forced to manually add them before adding them to a bridge.

This feels like adding new functionality to this code.  What is keeping
it from getting out of staging at this point in time?  I would prefer
for it to be moved out before adding new stuff to it.

thanks,

greg k-h

  parent reply	other threads:[~2020-07-15 14:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 13:34 [PATCH 0/6] staging: dpaa2-ethsw: cleanup of link state and MAC addresses Ioana Ciornei
2020-07-14 13:34 ` [PATCH 1/6] staging: dpaa2-ethsw: fix reported link state Ioana Ciornei
2020-07-14 13:34 ` [PATCH 2/6] staging: dpaa2-ethsw: ignore state interrupts when the interface is not running Ioana Ciornei
2020-07-14 13:34 ` [PATCH 3/6] staging: dpaa2-ethsw: use netif_running when checking for port up Ioana Ciornei
2020-07-14 13:34 ` [PATCH 4/6] staging: dpaa2-ethsw: disable switch ports are probe time Ioana Ciornei
2020-07-14 13:34 ` [PATCH 5/6] staging: dpaa2-ethsw: store version information of the DPSW object Ioana Ciornei
2020-07-14 13:34 ` [PATCH 6/6] staging: dpaa2-ethsw: setup MAC address of switch netdevices Ioana Ciornei
2020-07-15 14:10 ` Greg KH [this message]
2020-07-15 14:16   ` [PATCH 0/6] staging: dpaa2-ethsw: cleanup of link state and MAC addresses Ioana Ciornei

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=20200715141018.GA3377845@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=linux-kernel@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 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.