From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Jan Kundrát" <jan.kundrat@cesnet.cz>
Cc: Baruch Siach <baruch@tkos.co.il>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] ARM: mvebu_v7_defconfig: fix Ethernet on Clearfog
Date: Fri, 17 May 2019 21:53:56 +0200 [thread overview]
Message-ID: <87mujkzwkr.fsf@FE-laptop> (raw)
In-Reply-To: <871fc85b-5f0a-40a4-ade2-0701796bcd9a@cesnet.cz>
Jan Kundrát <jan.kundrat@cesnet.cz> writes:
>> Applied on mvebu/arm-5.3
>
> To me this looks like a 5.2 material because it fixes a regression that got
> introduced within the 5.2 cycle. Or did I get the process wrong and this is
> perhaps just a first step?
Well, this is just about configuration, I don't consider this is
something that is a candidate for a fix.
If there is a regression, then, it is maybe located in the Kconfig
dependency.
Of course I can change my mind with good arguments :)
Gregory
>
> Cheers,
> Jan
--
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
next prev parent reply other threads:[~2019-05-17 19:54 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 [this message]
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
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=87mujkzwkr.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=maxime.chevallier@bootlin.com \
--cc=rmk+kernel@armlinux.org.uk \
/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.