From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clockevents/clocksource: 3.12 fixes
Date: Tue, 12 Nov 2013 19:35:53 +0100 [thread overview]
Message-ID: <20131112183553.GQ14892@pengutronix.de> (raw)
In-Reply-To: <528234B9.7080402@linaro.org>
Hello,
On Tue, Nov 12, 2013 at 03:01:29PM +0100, Daniel Lezcano wrote:
>
> Hi Ingo and Thomas,
>
> this pull request has the following contain:
>
> * Laurent Pinchard fixed a missing a clk_put in case the
> registering of the sh_mtu[2] drivers fails.
>
> * Uwe Kleine-K?nig reuse clockevents_config_and_register for the
> at91rm9200_time timer as it was depending on the patch (commit
> a4578ea (clockevents: Sanitize ticks to nsec conversion).
>
> I don't know why Thomas's patch "clockevents: Sanitize ticks to nsec
> conversion" appears in the request log because it is not part of the
> patches interval I specified for git request pull. The diffstat does
> not show the files which should have been changed by the patch. In
> any case I kept the changelog untouched since it is what gives me
> git and maybe someone can tell me why it appears.
Look at:
git log --oneline --graph --boundary 97b9410..42ab380
Then you see that there is Thomas' patch twice. Once the version he
committed and sent to Linus (97b9410) and once the version that you get
as part of my pull request (a4578ea). To fix this (assuming you don't
care much about a stable tree), simply do:
git rebase 97b9410 42ab380
and let the result pull.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-11-12 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:01 [GIT PULL] clockevents/clocksource: 3.12 fixes Daniel Lezcano
2013-11-12 18:35 ` Uwe Kleine-König [this message]
2013-11-12 18:47 ` Daniel Lezcano
2013-11-12 22:57 ` Thomas Gleixner
2013-11-13 10:18 ` Daniel Lezcano
2013-11-13 10:36 ` Uwe Kleine-König
2013-11-13 13:53 ` Thomas Gleixner
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=20131112183553.GQ14892@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).