linux-kernel - Re: Linux 2.6.37-rc3 (fixmap build error)

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: <20101121181655.4996cdde.randy.dunlap@oracle.com>
Date:	Sun, 21 Nov 2010 18:16:55 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.37-rc3 (fixmap build error)

On Sun, 21 Nov 2010 15:43:18 -0800 Linus Torvalds wrote:

> Another week, another -rc.
> 
> And I have to say, I'm pretty happy with how quiet things have been.
> Of course,  maybe people are just lying low, waiting to ambush me next
> week with a flood of patches when I'm gone in Japan, all in order to
> try to be inconvenient. Because that's the kind of people kernel
> developers are.
> 
> But I'm going to just keep my fingers crossed, and hope that this
> means a calm release schedule. The fairly small ShortLog is appended,
> and looking at the dirstat, about 75% of the changes are to drivers
> (which is fairly normal), and over half of that is the DRM updates
> (which is higher than normal, and apparently brought on by everybody
> else being so quiet).


I thought that I saw a patch for this one, but I can't find it now.

on i386:
arch/x86/built-in.o: In function `fix_to_virt':
/usr/builds/linux-2.6.37-rc3/arch/x86/include/asm/fixmap.h:207: undefined reference to `__this_fixmap_does_not_exist'

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/