public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Yunjian Wang <wangyunjian@huawei.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: Have netpoll bring-up DSA management interface
Date: Tue, 17 Nov 2020 01:54:05 +0200	[thread overview]
Message-ID: <20201116235405.wkyyhqznocit4vj2@skbuf> (raw)
In-Reply-To: <20201116154710.20627867@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Mon, Nov 16, 2020 at 03:47:10PM -0800, Jakub Kicinski wrote:
> On Mon, 16 Nov 2020 15:20:37 -0800 Florian Fainelli wrote:
> > >> Florian for you patch specifially - can't we use
> > >> netdev_for_each_lower_dev()?  
> > > 
> > > Looks like I forgot to respond here, yes we could do that because we do
> > > call netdev_upper_dev_link() in net/dsa/slave.c. Let me re-post with
> > > that done.  
> > 
> > I remember now there was a reason for me to "open code" this, and this
> > is because since the patch is intended to be a bug fix, I wanted it to
> > be independent from: 2f1e8ea726e9 ("net: dsa: link interfaces with the
> > DSA master to get rid of lockdep warnings")
> > 
> > which we would be depending on and is only two-ish releases away. Let me
> > know if you prefer different fixes for different branches.
> 
> Ah, makes sense, we can apply this and then clean up in net-next. Just
> mention that in the commit message. FWIW you'll need to repost anyway
> once the discussion with Vladimir is resolved, because this is in the
> old patchwork instance :)

Yeah, I think Florian just wants netconsole to work in stable kernels,
which is a fair point. As for my 16-line patch that I suggested to him
in the initial reply, what do you think, would that be a "stable"
candidate? We would be introducing a fairly user-visible change
(removing one step that is mentioned as necessary in the documentation),
do you think it would benefit the users more to also have that behavior
change backported to all LTS kernels, or just keep it as something new
for v5.11? Either way, if it doesn't qualify as a patch for "stable",
then I guess Florian should just resubmit his patch on
net/core/netpoll.c.

  reply	other threads:[~2020-11-16 23:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 17:17 [PATCH net] net: Have netpoll bring-up DSA management interface Florian Fainelli
2020-10-19 20:02 ` Vladimir Oltean
2020-10-19 21:03   ` Florian Fainelli
2020-10-19 21:19     ` Vladimir Oltean
2020-10-21  1:12       ` Jakub Kicinski
2020-11-16 23:06         ` Florian Fainelli
2020-11-16 23:20           ` Florian Fainelli
2020-11-16 23:37             ` Vladimir Oltean
2020-11-16 23:47             ` Jakub Kicinski
2020-11-16 23:54               ` Vladimir Oltean [this message]
2020-11-17  0:04                 ` Jakub Kicinski
2020-11-17  0:12                   ` Vladimir Oltean
2020-11-17  0:16                     ` Florian Fainelli
2020-11-17  0:53 ` Vladimir Oltean

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=20201116235405.wkyyhqznocit4vj2@skbuf \
    --to=olteanv@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wangyunjian@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox