public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: torvalds@osdl.org
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Please pull x86-64 bug fixes
Date: Thu, 5 Oct 2006 19:10:25 +0200	[thread overview]
Message-ID: <200610051910.25418.ak@suse.de> (raw)


Linus,

Please pull 'for-linus' from 

  git://one.firstfloor.org/home/andi/git/linux-2.6

Andi Kleen:
      x86-64: Update defconfig
      i386: Update defconfig
      i386: Fix PCI BIOS config space access
      x86: Terminate the kernel stacks for the unwinder
      x86-64: Fix FPU corruption
      x86-64: Annotate interrupt frame backlink in interrupt handlers
      x86-64: Ignore alignment checks in kernel
      i386: Ignore alignment checks in kernel

Ingo Molnar:
      i386: fix rwsem build bug on CONFIG_M386=y

Jon Mason:
      x86-64: Calgary IOMMU: deobfuscate calgary_init
      x86-64: Calgary IOMMU: Fix off by one when calculating register space location
      x86-64: Calgary IOMMU: Update Jon's contact info
      x86-64: Calgary IOMMU: print PCI bus numbers in hex

Randy Dunlap:
      x86-64: Fix compilation without CONFIG_KALLSYMS

 MAINTAINERS                      |    2 +-
 arch/i386/defconfig              |   41 +++++++++++++++++++++++++++++-------
 arch/i386/kernel/process.c       |    6 ++++-
 arch/i386/kernel/traps.c         |   19 ++++++++++++++++-
 arch/i386/lib/semaphore.S        |    3 +++
 arch/i386/pci/direct.c           |    2 ++
 arch/i386/pci/init.c             |    4 ++++
 arch/x86_64/defconfig            |   43 +++++++++++++++++++++++++++++++-------
 arch/x86_64/kernel/entry.S       |    8 +++++++
 arch/x86_64/kernel/pci-calgary.c |   36 +++++++++++++++++++++-----------
 arch/x86_64/kernel/process.c     |    7 +++---
 arch/x86_64/kernel/setup64.c     |    2 +-
 arch/x86_64/kernel/traps.c       |   24 +++++++++++++++++++--
 13 files changed, 159 insertions(+), 38 deletions(-)

             reply	other threads:[~2006-10-05 17:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 17:10 Andi Kleen [this message]
2006-10-05 17:17 ` Please pull x86-64 bug fixes Jeff Garzik
2006-10-05 17:31   ` [discuss] " Andi Kleen
2006-10-05 17:43     ` Jeff Garzik
2006-10-05 17:53       ` Andi Kleen
2006-10-05 19:29         ` Jeff Garzik
2006-10-05 19:42           ` Andi Kleen
2006-10-05 20:02             ` Jeff Garzik
2006-10-05 20:10               ` Andi Kleen
2006-10-05 22:45               ` Linus Torvalds
2006-10-05 22:52                 ` Andi Kleen
2006-10-05 23:07                   ` Linus Torvalds
2006-10-05 23:21                     ` Andi Kleen
2006-10-05 23:36                     ` Jeff Garzik
2006-10-06  0:57                     ` Jeff Garzik
2006-10-06  1:29                       ` Linus Torvalds
2006-10-06 11:03                 ` Arjan van de Ven
2006-10-06 16:07                   ` Linus Torvalds
2006-10-06 16:19                     ` Arjan van de Ven
2006-10-06 22:01                     ` Rafael J. Wysocki
2006-10-06 22:31                       ` Duran, Leo
2006-10-06 23:06                         ` Jeff Garzik
2006-10-07  5:23                           ` Arjan van de Ven
2006-10-07  2:20                         ` Linus Torvalds
2006-10-08 20:59                           ` Duran, Leo
2006-10-08 22:42                             ` Linus Torvalds
2006-10-05 22:00         ` Alan Cox
2006-10-05 21:44           ` Andi Kleen
2006-10-06 11:14             ` Alan Cox
2006-10-16 12:21               ` Andi Kleen
2006-10-05 17:21 ` Linus Torvalds
2006-10-05 17:27   ` [discuss] " Andi Kleen
2006-10-05 22:59     ` Linus Torvalds
2006-10-05 23:05       ` Andi Kleen

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=200610051910.25418.ak@suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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