linux-kernel - Re: [PATCH] clocksource: time-efm32: Select CLKSRC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 16 Dec 2013 21:54:00 +0100
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Axel Lin <axel.lin@...ics.com>, linux-kernel@...r.kernel.org,
	kernel@...gutronix.de, Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH] clocksource: time-efm32: Select CLKSRC_MMIO

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/  |
--
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/