linux-kernel - Re: [PATCH 0/3] cpu freq: fix problems with work_on

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: <20090119172639.GA8011@elte.hu>
Date:	Mon, 19 Jan 2009 18:26:39 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Travis <travis@....com>
Cc:	Ingo Molnar <mingo@...hat.com>, Dave Jones <davej@...hat.com>,
	Rusty Russell <rusty@...tcorp.com.au>, cpufreq@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] cpu freq: fix problems with work_on_cpu usage in
	acpi-cpufreq [PULL request]


* Mike Travis <travis@....com> wrote:

> Ingo Molnar wrote:
> > * Mike Travis <travis@....com> wrote:
> > 
> >> Hi Ingo,
> >>
> >> If you are ready for these, I've pushed them to the cpus4096-for-ingo 
> >> tree.  (Note it's been renamed.)
> > 
> > that might be fine for v2.6.30, but we need separate patches in a 
> > separate branch, for all -git relevant fixes - in as safe way as 
> > possible.
> > 
> > 	Ingo
> 
> So you want me to create a separate branch for each patch?
> 
> And don't you think the fix to work_on_cpu should be put into 2.6.29?

Getting it into v2.6.29 is precisely the point: please put the essential 
fixes (and only the fixes) into a separate (single), -git based (i.e. not 
tip/cpus4096 based) branch that i can pull. The work_on_cpu() commit(s) 
would be part of that branch.

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