From: Sasha Levin <sashal@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
David Miller <davem@davemloft.net>, Andrew Lunn <andrew@lunn.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: add 3acca1dd to 4.19-stable
Date: Sat, 27 Apr 2019 10:00:22 -0400 [thread overview]
Message-ID: <20190427140022.GE17719@sasha-vm> (raw)
In-Reply-To: <1e6b7b7d-93ac-beed-d82d-db80fcb1a6a1@gmail.com>
On Fri, Apr 26, 2019 at 08:57:51PM +0200, Heiner Kallweit wrote:
>On 26.04.2019 12:55, Rasmus Villemoes wrote:
>> After ed8fe20205ac (net: dsa: mv88e6xxx: prevent interrupt storm caused
>> by mv88e6390x_port_set_cmode) got into 4.19-stable (as 4d8f5df0), a
>> non-CONFIG_NET_DSA_LEGACY build warns
>>
>> drivers/net/dsa/mv88e6xxx/chip.c:4635:13: warning:
>> ‘mv88e6xxx_ports_cmode_init’ defined but not used [-Wunused-function]
>>
>> I think 3acca1dd (net: dsa: mv88e6xxx: add call to
>> mv88e6xxx_ports_cmode_init to probe for new DSA framework) should be
>> added to the same stable trees that ed8fe20205ac was, at least 4.19.
>>
>That's right. Actually the referenced fix should have been applied to
>4.19, not sure why this wasn't done. On 5.0 it was applied.
>
>That's the confirmation from Dave that it was queued up for stable.
>https://marc.info/?l=linux-netdev&m=155173359712109&w=2
I've queued it for 4.19, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-04-27 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 10:55 add 3acca1dd to 4.19-stable Rasmus Villemoes
2019-04-26 18:57 ` Heiner Kallweit
2019-04-27 14:00 ` Sasha Levin [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=20190427140022.GE17719@sasha-vm \
--to=sashal@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=stable@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