From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Jan Kundrát" <jan.kundrat@cesnet.cz>,
"Russell King - ARM Linux admin" <linux@armlinux.org.uk>
Cc: Baruch Siach <baruch@tkos.co.il>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH] ARM: mvebu_v7_defconfig: fix Ethernet on Clearfog
Date: Wed, 12 Jun 2019 10:44:04 +0200 [thread overview]
Message-ID: <87muinp50r.fsf@FE-laptop> (raw)
In-Reply-To: <44a6f83c-f59a-4a6a-b38f-a204b38946c0@cesnet.cz>
Jan Kundrát <jan.kundrat@cesnet.cz> writes:
>>> I have not bisected, but I think that it is due to
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a10c1c8191e04c21769656c2ca8e1c69a6218954
>>>
>>> No guarantees there, though.
>>
>> Correct, which means it does need backporting to 5.1, since that was
>> introduced in the 5.1 merge window.
>
> ...which means that I made a mistake during my initial report. If it's in
> 5.1 already, then 5.1 could not have worked for me. Sorry for confusion,
> it's quite possible that I compared 5.2-rcX with 5.0.y.
So I added the Fixes tag and correct the commit log, mentioning 5.1
instead of 5.2.
The commit is in mvebu/fixes and for-next on
git://git.infradead.org/linux-mvebu.git and will be part of the Fixes
pull request I will do at the end of the week.
Gregory
>
> Jan
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-12 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 15:01 [PATCH] ARM: mvebu_v7_defconfig: fix Ethernet on Clearfog Jan Kundrát
2019-05-17 19:31 ` Gregory CLEMENT
2019-05-17 19:34 ` Jan Kundrát
2019-05-17 19:53 ` Gregory CLEMENT
2019-05-17 22:50 ` Jan Kundrát
2019-05-27 15:57 ` Jan Kundrát
2019-06-11 11:28 ` Gregory CLEMENT
2019-06-11 14:15 ` Jan Kundrát
2019-06-11 14:32 ` Russell King - ARM Linux admin
2019-06-11 15:04 ` Gregory CLEMENT
2019-06-11 15:12 ` Jan Kundrát
2019-06-11 15:31 ` Russell King - ARM Linux admin
2019-06-11 15:36 ` Jan Kundrát
2019-06-12 8:44 ` Gregory CLEMENT [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=87muinp50r.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=baruch@tkos.co.il \
--cc=davem@davemloft.net \
--cc=jan.kundrat@cesnet.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.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;
as well as URLs for NNTP newsgroup(s).