From: Greg KH <gregkh@linuxfoundation.org>
To: Ioana Ciornei <ciorneiioana@gmail.com>
Cc: David Miller <davem@davemloft.net>,
kuba@kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
olteanv@gmail.com, jiri@resnulli.us, ruxandra.radulescu@nxp.com,
netdev@vger.kernel.org, ioana.ciornei@nxp.com
Subject: Re: [PATCH net-next 00/15] dpaa2-switch: CPU terminated traffic and move out of staging
Date: Thu, 11 Mar 2021 08:05:04 +0100 [thread overview]
Message-ID: <YEnBINkt+CSP8BCe@kroah.com> (raw)
In-Reply-To: <YEnA/fSHjDS2p19U@kroah.com>
On Thu, Mar 11, 2021 at 08:04:29AM +0100, Greg KH wrote:
> On Thu, Mar 11, 2021 at 08:54:37AM +0200, Ioana Ciornei wrote:
> > On Wed, Mar 10, 2021 at 03:13:10PM -0800, David Miller wrote:
> > > From: Greg KH <gregkh@linuxfoundation.org>
> > > Date: Wed, 10 Mar 2021 15:12:57 +0100
> > >
> > > > Yes, either I can provide a stable tag to pull from for the netdev
> > > > maintainers, or they can just add the whole driver to the "proper" place
> > > > in the network tree and I can drop the one in staging entirely. Or
> > > > people can wait until 5.13-rc1 when this all shows up in Linus's tree,
> > > > whatever works best for the networking maintainers, after reviewing it.
> > >
> > > I've added this whole series to my tree as I think that makes things easiest
> > > for everyone.
> > >
> > > Thanks!
> >
> > Sorry for bothering you again.. but it seems that Greg has also added
> > the first 14 patches to staging-next. I just want to make sure that the
> > linux-next will be happy with these patches being in 2 trees.
>
> It should, git is nice :)
>
> I can also just drop them from my staging tree as well, that's trivial.
Ah, just saw your "these are broken" email, I'll go drop these.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-11 7:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 12:14 [PATCH net-next 00/15] dpaa2-switch: CPU terminated traffic and move out of staging Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 01/15] staging: dpaa2-switch: remove broken learning and flooding support Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 02/15] staging: dpaa2-switch: fix up initial forwarding configuration done by firmware Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 03/15] staging: dpaa2-switch: remove obsolete .ndo_fdb_{add|del} callbacks Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 04/15] staging: dpaa2-switch: get control interface attributes Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 05/15] staging: dpaa2-switch: setup buffer pool and RX path rings Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 06/15] staging: dpaa2-switch: setup dpio Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 07/15] staging: dpaa2-switch: handle Rx path on control interface Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 08/15] staging: dpaa2-switch: add .ndo_start_xmit() callback Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 09/15] staging: dpaa2-switch: enable the control interface Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 10/15] staging: dpaa2-switch: properly setup switching domains Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 11/15] staging: dpaa2-switch: move the notifier register to module_init() Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 12/15] staging: dpaa2-switch: accept only vlan-aware upper devices Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 13/15] staging: dpaa2-switch: add fast-ageing on bridge leave Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 14/15] staging: dpaa2-switch: prevent joining a bridge while VLAN uppers are present Ioana Ciornei
2021-03-10 12:14 ` [PATCH net-next 15/15] staging: dpaa2-switch: move the driver out of staging Ioana Ciornei
2021-03-10 12:44 ` [PATCH net-next 00/15] dpaa2-switch: CPU terminated traffic and move " Greg KH
2021-03-10 13:47 ` Ioana Ciornei
2021-03-10 14:12 ` Greg KH
2021-03-10 14:18 ` Vladimir Oltean
2021-03-10 22:12 ` Ioana Ciornei
2021-03-10 23:13 ` David Miller
2021-03-11 6:54 ` Ioana Ciornei
2021-03-11 7:04 ` Greg KH
2021-03-11 7:05 ` Greg KH [this message]
2021-03-10 23:20 ` patchwork-bot+netdevbpf
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=YEnBINkt+CSP8BCe@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@lunn.ch \
--cc=ciorneiioana@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=ruxandra.radulescu@nxp.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 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.