From: Jeff Garzik <jgarzik@pobox.com>
To: ak@suse.de, linux-kernel@vger.kernel.org
Subject: [AMD64 0/3] description and URLS
Date: Sat, 25 Oct 2003 14:29:35 -0400 [thread overview]
Message-ID: <20031025182935.GA12165@gtf.org> (raw)
Requesting permission to send this to Linus...
BK users:
bk pull bk://kernel.bkbits.net/jgarzik/bum-2.5
Patch available at
ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.0-test8-bk5-amd64-1.patch.bz2
This will update the following files:
arch/x86_64/ia32/syscall32.c | 4 +-
arch/x86_64/kernel/acpi/boot.c | 69 +++++++++++++++++++++++++++------------
arch/x86_64/kernel/bluesmoke.c | 8 ++--
arch/x86_64/kernel/setup.c | 2 -
arch/x86_64/kernel/x8664_ksyms.c | 2 -
5 files changed, 58 insertions(+), 27 deletions(-)
through these ChangeSets:
<jgarzik@redhat.com> (03/10/25 1.1354)
[BK] ignore x86-64 build generated files
<jgarzik@redhat.com> (03/10/25 1.1353)
[AMD64] fix bcopy prototype
Linus recently fixed the version in lib/
<jgarzik@redhat.com> (03/10/25 1.1352)
[AMD64] add acpi_pic_set_level_irq
ACPI guys broke the AMD64 build. Adding this function fixes it.
<jgarzik@redhat.com> (03/10/25 1.1351)
[AMD64] Fix C99-ish mix of declarations and code.
reply other threads:[~2003-10-25 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031025182935.GA12165@gtf.org \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.