From: Greg KH <gregkh@linuxfoundation.org>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [patch 1/1] drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case
Date: Fri, 16 Oct 2020 10:01:14 +0200 [thread overview]
Message-ID: <20201016080114.GA1355531@kroah.com> (raw)
In-Reply-To: <87wnzr6bun.fsf@lechat.rtp-net.org>
On Thu, Oct 15, 2020 at 12:08:00PM +0200, Arnaud Patard wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
>
> > On Thu, Oct 15, 2020 at 11:32:15AM +0200, Arnaud Patard wrote:
> >> commit d934423ac26ed373dfe089734d505dca5ff679b6 upstream.
> >>
> >> Orion5.x systems are still using machine files and not device-tree.
> >> Commit 96cb4342382290c9 ("net: mvmdio: allow up to three clocks to be
> >> specified for orion-mdio") has replaced devm_clk_get() with of_clk_get(),
> >> leading to a oops at boot and not working network, as reported in
> >> https://lists.debian.org/debian-arm/2019/07/msg00088.html and possibly in
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908712.
> >>
> >> Link: https://lists.debian.org/debian-arm/2019/07/msg00088.html
> >> Fixes: 96cb4342382290c9 ("net: mvmdio: allow up to three clocks to be specified for orion-mdio")
> >> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> >> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> >> Signed-off-by: David S. Miller <davem@davemloft.net>
> >>
> >
> > What stable tree(s) are you asking for this to be backported to?
>
> oops, forgot to put it in the mail subject. It's for 4.19.X, which is
> used in Debian stable.
Also works on 4.14.y, so I've put it there as well.
thanks,
greg k-h
prev parent reply other threads:[~2020-10-16 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 9:32 [patch 1/1] drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case Arnaud Patard
2020-10-15 10:04 ` Greg KH
2020-10-15 10:08 ` Arnaud Patard
2020-10-16 8:01 ` Greg KH [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=20201016080114.GA1355531@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@lunn.ch \
--cc=arnaud.patard@rtp-net.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).