From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Axel Lin <axel.lin@ingics.com>, Dinh Nguyen <dinguyen@altera.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] clocksource/clockevents fixes for 3.13
Date: Tue, 10 Dec 2013 15:30:53 +0100 [thread overview]
Message-ID: <52A7259D.5080609@linaro.org> (raw)
In-Reply-To: <20131210133633.GB31366@gmail.com>
On 12/10/2013 02:36 PM, Ingo Molnar wrote:
>
> * Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
>> On 12/10/2013 01:20 PM, Ingo Molnar wrote:
>>>
>>> * Daniel Lezcano <daniel.lezcano@linaro.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
prev parent reply other threads:[~2013-12-10 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:39 [GIT PULL] clocksource/clockevents fixes for 3.13 Daniel Lezcano
2013-12-10 12:20 ` Ingo Molnar
2013-12-10 12:59 ` Daniel Lezcano
2013-12-10 13:36 ` Ingo Molnar
2013-12-10 14:30 ` Daniel Lezcano [this message]
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=52A7259D.5080609@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=axel.lin@ingics.com \
--cc=dinguyen@altera.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
/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