From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: drivers for v4.9 (#1)
Date: Tue, 20 Sep 2016 09:09:29 +0200 [thread overview]
Message-ID: <87wpi76o9i.fsf@free-electrons.com> (raw)
In-Reply-To: <4134529.ol6KhRYAQp@wuerfel> (Arnd Bergmann's message of "Tue, 20 Sep 2016 00:16:41 +0200")
Hi Arnd,
On mar., sept. 20 2016, Arnd Bergmann <arnd@arndb.de> wrote:
> On Wednesday, September 14, 2016 5:35:10 PM CEST Gregory CLEMENT wrote:
>> mvebu drivers for 4.9 (part 1)
>>
>> - Add pinctrl and clk support for the Orion5x SoC mv88f5181 variant
>>
>> ----------------------------------------------------------------
>> Jamie Lentin (2):
>> clk: mvebu: Add clk support for the orion5x SoC mv88f5181
>> pinctrl: mvebu: orion5x: Generalise mv88f5181l support for 88f5181
>>
>> .../devicetree/bindings/clock/mvebu-core-clock.txt | 1 +
>> .../bindings/pinctrl/marvell,orion-pinctrl.txt | 4 +-
>> drivers/clk/mvebu/orion.c | 70 ++++++++++++++++++++++
>> drivers/pinctrl/mvebu/pinctrl-orion.c | 23 +++----
>> 4 files changed, 86 insertions(+), 12 deletions(-)
>
> I see this touches pinctrl and clk drivers, but none of the maintainers are
> on Cc for this pull request, nor have they provided an Ack for the patches
> according to your git log.
>
> Why did you not send the driver changes to them?
My bad sorry. The changes only touch data (adding new varaiant of the
orion5x), are very trivial and won't cause any merge
conflict. Furthermore there is depency with the other pacthes in the
mvebu branches and we already did this in the past to avoid dependecy
between subsystem. _But_ I should have asked the acked-by from the
drivers maintainers, it was the way we wolved it in the past and I
forgot it.
>
> Not pulled for now, until this is resolved, sorry.
If the drivers maintainer for pinctrl and clk give their acked-by do you
agree to take it for 4.9?
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2016-09-20 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 15:35 [GIT PULL] ARM: mvebu: drivers for v4.9 (#1) Gregory CLEMENT
2016-09-19 22:16 ` Arnd Bergmann
2016-09-20 7:09 ` Gregory CLEMENT [this message]
2016-09-20 21:51 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2016-09-21 10:18 Gregory CLEMENT
2016-09-21 20:37 ` 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=87wpi76o9i.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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