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]
Message-ID: <7195611.gCcafMWC85@vostro.rjw.lan>
Date:	Mon, 24 Jun 2013 12:59:07 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	cpufreq@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>
Subject: Re: [GIT PULL] ARM: CPUFreq updates for 3.11

On Monday, June 24, 2013 04:12:29 PM Viresh Kumar wrote:
> On 24 June 2013 16:19, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > On Monday, June 24, 2013 11:20:35 AM Viresh Kumar wrote:
> >> Hi Rafael,
> >>
> >> This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
> >> sequence". It contains changes specific to cpufreq core and ARM drivers.
> >>
> >> I have left changes to non-ARM cpufreq drivers from this pull request. See if
> >> you can take them for 3.11.
> >>
> >> The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
> >>
> >>   Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
> >>
> >> are available in the git repository at:
> >>
> >>   git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification-arm
> >>
> >> for you to fetch changes up to f2d65dd0d573e6961165f0be35bac84997b9e707:
> >
> > Well, this contains changes that aren't specific to ARM as far as I can say.
> 
> Yeah, the first patch touches core. How do you want to proceed with this one
> then? You will apply them from mail? Or you will apply first patch (core cpufreq
> one) and I should send pull request without it?

In your original series that patch was the last one.  What made you change your
mind and put it in front?

Rafael

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