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] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 Oct 2013 08:04:43 -0700
From:	Mike Turquette <mturquette@...aro.org>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Peter De Schrijver <pdeschrijver@...dia.com>,
	Prashant Gaikwad <pgaikwad@...dia.com>,
	Thierry Reding <thierry.reding@...il.com>,
	Rob Herring <rob.herring@...xeda.com>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: pull request for tegra clocks (resend with some CCs added this time)

I'm happy for the changes to be based on an -rc or clk-next. Either is fine.

Thanks,
Mike

On Tue, Oct 15, 2013 at 8:42 AM, Stephen Warren <swarren@...dotorg.org> wrote:
> On 10/15/2013 09:36 AM, Peter De Schrijver wrote:
>> The following changes since commit a0cf1abc25ac197dd97b857c0f6341066a8cb1cf:
>>
>>   Add linux-next specific files for 20130927 (2013-09-27 18:48:50 +1000)
>>
>> are available in the git repository at:
>>   git://nv-tegra.nvidia.com/user/pdeschrijver/linux.git tegra-clk-patches-0
>
> ??? That won't merge into Mike's tree correctly. The pull request should
> be based on a -rc or final release in the Linus tree, e.g. based on
> v3.12-rc1. Otherwise, if Mike merges this, it will pull in all patches
> from other subsystems that went into linux-next.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ