From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] Add DT support for netxbig LEDs
Date: Mon, 30 Mar 2015 15:29:41 +0200 [thread overview]
Message-ID: <55194FC5.6080902@free-electrons.com> (raw)
In-Reply-To: <20150330132240.GB8688@io.lakedaemon.net>
Hi Simon,
[...]
>>> Hi Gregory, Andrew and Jason,
>>>
>>> This patch set seems stuck. I believe that Bryan is probably too busy to
>>> handle it...
>>>
>>> Is that possible to merge it via the mvebu tree ? Since only some LaCie
>>> boards are impacted, I think it could make sense.
>>
>> Hi Simon
>>
>> Hard one. I also have a driver stuck in led limbo.
>>
>> Last time we took a fix via mvebu, it all went messy at the last
>> minute. We made it very clear to Bryon we planned to take a patch via
>> mvebu, we had queued it via mvebu, we had sent a pull request to
>> arm-soc, all with no reply from Bryon. Only at the last minute did he
>> jump in, pull it himself and send it to Linus. That caused Olof all
>> sorts of problems with his tree.
>
> It's also good to keep in mind the workflow of driver maintainers who push
> directly to Linus. They send PRs during the merge window, and don't
> necessarily spend too much time in -next. Which means, if they have good
> filters running on lkml, they just sit down a week or so before the merge
> window and apply everything they have pending.
>
> For those of us who are feeding arm-soc, and are accustomed to getting things
> in early, this can be nerve-wracking.
>
> Brian has demonstrated that he does pick things up and get them merged. We
> just need to make sure that what he picks up is well tested and reviewed when
> he gets to it. Since there won't be time for another revision before the merge
> window. But hey, that's what -rc's are for. :-P
>
At least what I can do is creating a led branch and merged it in the mvebu/for-next
branch. It will allow us to be more confident for the merge window.
Thanks,
Gregory
>> To stop that happening again, i think we need an Acked-by from Bryan.
>
> I agree.
>
> thx,
>
> Jason.
>
--
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:[~2015-03-30 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:04 [PATCH 0/3] Add DT support for netxbig LEDs Simon Guinot
2015-02-23 15:04 ` [PATCH 1/3] leds: netxbig: add device tree binding Simon Guinot
2015-02-23 15:04 ` [PATCH 2/3] ARM: Kirkwood: add LED DT entries for netxbig boards Simon Guinot
2015-02-23 15:04 ` [PATCH 3/3] ARM: mvebu: remove static LED setup " Simon Guinot
2015-03-09 9:41 ` [PATCH 0/3] Add DT support for netxbig LEDs Simon Guinot
2015-03-16 16:01 ` Gregory CLEMENT
2015-03-30 8:30 ` Simon Guinot
2015-03-30 12:30 ` Andrew Lunn
2015-03-30 13:22 ` Jason Cooper
2015-03-30 13:29 ` Gregory CLEMENT [this message]
2015-03-30 13:46 ` Jason Cooper
2015-03-30 14:20 ` Gregory CLEMENT
2015-03-23 10:31 ` Simon Guinot
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=55194FC5.6080902@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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