[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52A7259D.5080609@linaro.org>
Date: Tue, 10 Dec 2013 15:30:53 +0100
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Ingo Molnar <mingo@...nel.org>
CC: Thomas Gleixner <tglx@...utronix.de>,
Axel Lin <axel.lin@...ics.com>,
Dinh Nguyen <dinguyen@...era.com>,
Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
Marc Zyngier <marc.zyngier@....com>,
Thierry Reding <thierry.reding@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] clocksource/clockevents fixes for 3.13
On 12/10/2013 02:36 PM, Ingo Molnar wrote:
>
> * Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>
>> On 12/10/2013 01:20 PM, Ingo Molnar wrote:
>>>
>>> * Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>>>
>>>>
>>>> Hi Thomas,
>>>>
>>>> here are the fixes for 3.13 based on timers/urgent
>>>
>>> Please generally also post the patches to make it easier to review
>>> them.
>>
>> Hi Ingo,
>>
>> what do you mean by "also post the patches" ? The patches were
>> posted in the mailing lists and I picked them up after people
>> reviewed them.
>
> For example I found none of Dinh Nguyen's two patches on lkml.
>
> Even if they were on lkml it's generally good practice to post patches
> for pull requests even if they are mostly resends of existing patches,
> especially for an urgent tree. That makes it easier for people to
> chime in on patches.
>
>> Or shall I give a combined diff when sending the PR ?
>
> Individual patches posted as a threaded reply to the pull request mail
> would be nice - those are easy for other people to ignore, yet they
> are informative to people who are interested in the series.
Ah, ok I see. Will do next time.
Thanks !
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists