From: Andreas Haumer <andreas@xss.co.at>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.27-pre6
Date: Thu, 17 Jun 2004 15:01:19 +0200 [thread overview]
Message-ID: <40D1961F.7090804@xss.co.at> (raw)
In-Reply-To: <20040616183343.GA9940@logos.cnet>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Marcelo,
Marcelo Tosatti wrote:
> Hi,
>
> Here goes -pre6. It contains a significant amount of USB fixes, JFS update,
> netfilter/sctp fixes, CDROM driver update, tg3 update, SPARC/Alpha fixes.
>
> And more importantly the FPU x86/x86-64 crash fix.
>
> Read the detailed changelog for more details.
>
As already reported for -pre5 and still valid for -pre6,
"make xconfig" is broken due to changes in drivers/hotplug/Config.in
The attached (trivial) patch fixes this problem.
HTH
Regards,
- - andreas
- --
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFA0ZYZxJmyeGcXPhERAvJ1AJ0dA82kQ+jk0sdQiF5whMa+nvfxVQCghCGh
JSw80qVZNyIWwUZLslMdJ/k=
=3eBJ
-----END PGP SIGNATURE-----
[-- Attachment #2: hotplug_xconfig_HRT.patch --]
[-- Type: text/plain, Size: 964 bytes --]
--- linux-2.4.27pre6/drivers/hotplug/Config.in.orig 2004-06-17 14:16:42.000000000 +0200
+++ linux-2.4.27pre6/drivers/hotplug/Config.in 2004-06-17 14:40:02.000000000 +0200
@@ -17,7 +17,7 @@
dep_tristate ' SHPC PCI Hotplug driver' CONFIG_HOTPLUG_PCI_SHPC $CONFIG_HOTPLUG_PCI
dep_mbool ' Use polling mechanism for hot-plug events (for testing purpose)' CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE $CONFIG_HOTPLUG_PCI_SHPC
if [ "$CONFIG_ACPI" = "n" ]; then
-dep_mbool ' For AMD SHPC only: Use $HRT for resource/configuration' CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY $CONFIG_HOTPLUG_PCI_SHPC
+dep_mbool ' For AMD SHPC only: Use HRT for resource/configuration' CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY $CONFIG_HOTPLUG_PCI_SHPC
fi
dep_tristate ' PCI Express Hotplug driver' CONFIG_HOTPLUG_PCI_PCIE $CONFIG_HOTPLUG_PCI
dep_mbool ' Use polling mechanism for hot-plug events (for testing purpose)' CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE $CONFIG_HOTPLUG_PCI_PCIE
prev parent reply other threads:[~2004-06-17 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 18:33 Linux 2.4.27-pre6 Marcelo Tosatti
2004-06-17 9:40 ` Linux 2.4.27-pre6: visor.c Eyal Lebedinsky
2004-06-17 9:48 ` Linux 2.4.27-pre6: visor.c (patch) Eyal Lebedinsky
2004-06-17 10:06 ` ip6_tables warning (was: Re: Linux 2.4.27-pre6) Geert Uytterhoeven
2004-06-17 10:13 ` ip6_tables warning YOSHIFUJI Hideaki / 吉藤英明
2004-06-17 17:12 ` David S. Miller
2004-06-17 19:05 ` igmp warning (was: Re: Linux 2.4.27-pre6) Geert Uytterhoeven
2004-06-17 19:09 ` David S. Miller
2004-06-17 10:10 ` rwsem-spinlock error " Geert Uytterhoeven
2004-06-17 10:35 ` rwsem-spinlock error Nick Piggin
2004-06-17 13:13 ` Nuno Monteiro
2004-06-17 13:01 ` Andreas Haumer [this message]
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=40D1961F.7090804@xss.co.at \
--to=andreas@xss.co.at \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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