mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc3 (fixmap build error)
Date: Sun, 21 Nov 2010 18:16:55 -0800	[thread overview]
Message-ID: <20101121181655.4996cdde.randy.dunlap@oracle.com> (raw)
In-Reply-To: <AANLkTi=Di4UQMYyJ_wpZ6N=NZt1+3EeXL7FUsBX004YL@mail.gmail.com>

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

  reply	other threads:[~2010-11-22  2:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 23:43 Linux 2.6.37-rc3 Linus Torvalds
2010-11-22  2:16 ` Randy Dunlap [this message]
2010-11-22  4:33   ` Linux 2.6.37-rc3 (fixmap build error) Linus Torvalds
2010-11-22  5:44     ` Andrew Morton
2010-11-22 16:20       ` Randy Dunlap
2010-11-24 10:12 ` Linux 2.6.37-rc3 Américo Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101121181655.4996cdde.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome