linux-kernel - Re: linux-next: cpufreq-current tree build warning

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]

Message-ID: <20090917031759.GB30706@redhat.com>
Date:	Wed, 16 Sep 2009 23:17:59 -0400
From:	Dave Jones <davej@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kurt Roeckx <kurt@...ckx.be>
Subject: Re: linux-next: cpufreq-current tree build warning

On Thu, Sep 17, 2009 at 12:55:56PM +1000, Stephen Rothwell wrote:
 > so, no.
 > (origin/master is Linus' tree of about 2 hours ago, commit
 > ab86e5765d41a5eb4239a1c04d613db87bea5ed8 "Merge
 > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core-2.6")
 > 
 > Looking further, this is the cpureq-current tree I am complaining about,
 > in the cpufreq tree, you also have:

Oh, from the 'fixes' branch ?  Just drop that for now, and only pick up 'next'
(though next pull request went to linus today, so the whole thing should be
 gone soon).

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