From: wwp <subscript-GANU6spQydw@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.4.24 patch apply failed on vanilla kernel
Date: Fri, 9 Jan 2004 11:33:24 +0100 [thread overview]
Message-ID: <20040109113324.6d808e4a@tethys> (raw)
In-Reply-To: <1073643569.2447.66.camel-D2Zvc0uNKG8@public.gmane.org>
Hi Len Brown,
On 09 Jan 2004 05:19:29 -0500 Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> Two problems here -- both caused my me -- both now fixed.
>
> 1. I mis-merged the line in smpboot.c
> when I first found and fixed that bug i replaced NR_CPUS
> with MAX_APICS, which made perfect sense for the non-numa
> case where MAX_APICS is 16. wli checked in the BITS_PER_LONG
> fix (32) and I mistakenly over-wrote it -- now restored.
>
> 2. Marcelo re-named the 2.4.24 bk tree to be 2.4.25
> and quickly released a new 2.4.24 tree with just a couple of
> changes. Until tonight, my ACPI patch on kernel.org was
> against the 'old' 2.4.24. I've since updated both the trees
> at http://linux-acpi.bkbits.net/ as well as the plain patches
> up on http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches
>
> Let me know if I missed anything.
Thanx for the clarification!
Regards,
--
wwp
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-09 10:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 12:46 2.4.24 patch apply failed on vanilla kernel Marcel Meckel
[not found] ` <20040107134658.5afa9142.acpi-X2Xph2rMQzhn68oJJulU0Q@public.gmane.org>
2004-01-07 14:25 ` wwp
[not found] ` <20040107152540.574f5882-qdKmdXVU2OY@public.gmane.org>
2004-01-07 16:07 ` Micha Feigin
[not found] ` <20040107160711.GB12275-4cxDFgrrBECgSpxsJD1C4w@public.gmane.org>
2004-01-07 16:38 ` wwp
2004-01-07 14:53 ` wwp
[not found] ` <20040107155325.5bfceba0-qdKmdXVU2OY@public.gmane.org>
2004-01-07 15:39 ` Marcel Meckel
[not found] ` <20040107163907.391c146e.acpi-X2Xph2rMQzhn68oJJulU0Q@public.gmane.org>
2004-01-07 15:50 ` wwp
[not found] ` <20040107165054.1fbfc829-qdKmdXVU2OY@public.gmane.org>
2004-01-07 20:01 ` Sérgio Monteiro Basto
[not found] ` <1073505678.7422.24.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2004-01-07 21:54 ` wwp
2004-01-07 21:56 ` wwp
[not found] ` <20040107225650.388f96d4-qdKmdXVU2OY@public.gmane.org>
2004-01-09 10:19 ` Len Brown
[not found] ` <1073643569.2447.66.camel-D2Zvc0uNKG8@public.gmane.org>
2004-01-09 10:33 ` wwp [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 6:16 Yu, Luming
2004-01-08 9:46 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CA3-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-08 10:52 ` Luca Capello
2004-01-08 22:13 ` Brian Perkins
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=20040109113324.6d808e4a@tethys \
--to=subscript-ganu6spqydw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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