From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Marek Behún" <kabel@kernel.org>, "Arnd Bergmann" <arnd@arndb.de>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [GIT PULL v2] ARM: mvebu: fixes for v5.9 (#1)
Date: Mon, 26 Oct 2020 17:37:25 +0100 [thread overview]
Message-ID: <87sga1c5a2.fsf@BL-laptop> (raw)
In-Reply-To: <20201026150131.3da50593@kernel.org>
Hello Arnd and Marek,
I don't know why but I didn't receive the email from Arnd. It is thanks
to Marek answer that I was able to see it. I also don't see Arn email in
the arm-kernel archive mailing list;
http://lists.infradead.org/pipermail/linux-arm-kernel/2020-October/date.html
> On Mon, 26 Oct 2020 10:23:07 +0100
> Arnd Bergmann <arnd@arndb.de> wrote:
>
>> On Mon, Oct 5, 2020 at 3:01 PM Gregory CLEMENT
>> <gregory.clement@bootlin.com> wrote:
>> >
>> > git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-fixes-5.9-1
>> >
>> > for you to fetch changes up to 0b58725fb9a446890c1fd28fc6c9e393ce21acb7:
>> >
>> > ARM: mvebu: drop pointless check for coherency_base (2020-09-24 10:19:06 +0200)
>> >
>> > ----------------------------------------------------------------
>> > mvebu fixes for 5.9 (part 1)
>> >
>> > - Allow to use correct MAC address for particular DSA slaves /
>> > ethernet ports on Espressobin (Armada 3720)
>> >
>> > - Remove incorrect check in ll_get_coherency_base() used for Armada
>> > 370/XP SoCs.
>> >
>>
>> Hi Gregory,
>>
>> as you may have noticed, your last set of pull requests didn't make
>> it in so far, sorry about that.
Is there a way to avoid this in the future ?
For the last release I was not notified that the pull request was
merged, so I wasn't worried about it. I was surprised to not see my
branch in the arm-soc tree, but i though that the branch was not
updated on the server.
>>
>> I have taken this one into the arm/fixes branch now and
>> will send it in the next few days. I see that one of the fixes has a
>> Cc:stable tag and the other one is not urgent, so they will make it
>> into the stable kernels.
>>
>> The other two branches you sent are not part of v5.10. Let me
>> know if you prefer me to pick these up for v5.11 unchanged or
>> you'd rather rebase the contents and send new pull requests.
Actually there was 3 other branch: dt, dt64 and arm. I will rebase them.
However I wonder if it could worse to apply the patch "MAINTAINERS:
switch mvebu tree to kernel.org" to 5.10, as it will help people to know
where is located the current development branch.
>>
>> I see Marek Behún sent three more fixes Cc:soc@kernel.org.
>> I assume you are going to pick these up and send a pull
>> request for them, but I can pick them up directly if that helps.
>>
>> Arnd
>
> Arnd, Gregory, these fixes are not stable yet, please don't pull them.
> We will send a new version after we end up our discussion about that
> issue with Marvell.
OK, so I will submit a new pull request for fixes once the new version
will be submitted.
Thanks,
Gregory
>
> Marek
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
0
_______________________________________________
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:[~2020-10-26 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 13:01 [GIT PULL v2] ARM: mvebu: fixes for v5.9 (#1) Gregory CLEMENT
[not found] ` <CAK8P3a1Am-xH-_vjaUdE3uyns-yMDgQs2-oo41YeSZNO-DQoEQ@mail.gmail.com>
2020-10-26 14:01 ` Marek Behún
2020-10-26 16:37 ` Gregory CLEMENT [this message]
2020-10-26 19:01 ` Arnd Bergmann
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=87sga1c5a2.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@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).