From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Axel Lin <axel.lin@ingics.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] clocksource: time-efm32: Select CLKSRC_MMIO
Date: Mon, 16 Dec 2013 21:54:00 +0100 [thread overview]
Message-ID: <20131216205400.GD14866@pengutronix.de> (raw)
In-Reply-To: <52AF5DB5.8090302@linaro.org>
Hello Daniel,
On Mon, Dec 16, 2013 at 09:08:21PM +0100, Daniel Lezcano wrote:
> On 12/10/2013 05:05 PM, Uwe Kleine-König wrote:
> >On Tue, Dec 10, 2013 at 02:29:42PM +0100, Daniel Lezcano wrote:
> >>I sent the PR with this patch. If everything is ok, it should be in
> >>the next -rc.
> >ok. Thanks for your quick reply.
It seems to have missed 3.13-rc4 btw :-(
> >It would be great if your tree were included in linux-next. Don't you
> >think this is feasible?
>
> Well, yes it could be a good idea. But if you are suggesting to use
> linux-next for the fixes, that should be already taken into account
> with the #auto-latest branch of tip.
I might be wrong, but it seems that the window when the patches are in
your tree but not yet in tip is big. At least I hit that window I think
three times already.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2013-12-16 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 2:15 Axel Lin
2013-11-20 9:22 ` Uwe Kleine-König
2013-12-10 13:24 ` Uwe Kleine-König
2013-12-10 13:29 ` Daniel Lezcano
2013-12-10 16:05 ` Uwe Kleine-König
2013-12-16 20:08 ` Daniel Lezcano
2013-12-16 20:54 ` Uwe Kleine-König [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=20131216205400.GD14866@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=axel.lin@ingics.com \
--cc=daniel.lezcano@linaro.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®