From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Marek Behún" <kabel@kernel.org>, "Arnd Bergmann" <arnd@kernel.org>
Cc: pali@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: mvebu changes
Date: Fri, 12 Mar 2021 09:49:48 +0100 [thread overview]
Message-ID: <87ft10kb83.fsf@BL-laptop> (raw)
In-Reply-To: <20210312093606.7669f488@kernel.org>
Hello Marek,
> Hello Arnd,
>
> I together with Pali Rohar have some time ago sent some updates for
> Turris MOX / ESPRESSObin (mvebu platform), but it seems that Gregory
> Clement, the maintainer for mvebu, is currently unavailable:
> - the series
> [PATCH mvebu v3 00/10] Armada 37xx: Fix cpufreq changing
> base CPU speed to 800 MHz from 1000 MHz
> was sent almost 3 weeks ago, already with Tested-by tags
3 weeks ago the windows lerge for arm-soc was closed.
> - some more patches for turris-mox-rwtm were sent just recently
The other patches you sent was submitted only 4 days ago, so I don't
think it was so long ago.
Gregory
>
> We are curious if it is possible for you to merge these changes
> directly. We both have kernel.org account, so we can prepare
> pull-requests, or we can resend these patches to ML.
>
> Thank you.
>
> Marek
--
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:[~2021-03-12 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 8:36 mvebu changes Marek Behún
2021-03-12 8:49 ` Gregory CLEMENT [this message]
2021-03-12 9:02 ` Marek Behún
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=87ft10kb83.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=arnd@kernel.org \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pali@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 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.