From: Adrian Bunk <bunk@fs.tum.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Alan Cox <alan@redhat.com>,
johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20-rc4-ac1
Date: Fri, 29 Nov 2002 17:16:33 +0100 [thread overview]
Message-ID: <20021129161633.GG6981@fs.tum.de> (raw)
In-Reply-To: <1568261310.1038471302@[10.10.2.3]>
On Thu, Nov 28, 2002 at 08:15:02AM -0800, Martin J. Bligh wrote:
> > Martin, could you please review whether the patch below which does the
> > following is correct?
> >
> > - kill the last occurence of CLUSTERED_APIC_NUMAQ
> > - only one definition of PCI_CONF1_ADDRESS is needed
> > (#ifndef CONFIG_MULTIQUAD the BUS2LOCAL() has no effect)
> > - fix an #endif comment
>
> I'm confused at to what made this break recently .... what release
> did this break on? Either it was something very recent, everyone
> else is asleep, or you're doing something wierd (like compling with
> MULTIQUAD on?)
Yes, I tried a compilation with MULTIQUAD on.
The "very recent" might be that I'm talking about -ac (look at the
Subject).
> CLUSTERED_APIC_NUMAQ is a part of the Summit patch introduction,
> where John (cc'ed) splits clustered_apic_mode from a boolean into
> a switch (in 2.4 ... I did 2.5 differently). Maybe we merged half
> of a summit patch somehow, and didn't get the define?
>...
First of all:
I noticed this problem while doing a compile-only test, I have no real
knowledge of the code.
In 2.4.20-pre the following change was made in several places:
clustered_apic_mode -> (clustered_apic_mode == CLUSTERED_APIC_NUMAQ)
In 2.4.20-pre-ac they were changed again, this time
(clustered_apic_mode == CLUSTERED_APIC_NUMAQ) -> clustered_apic_logical
According to grep the occurence of CLUSTERED_APIC_NUMAQ my patch changes
was the last one _in the whole kernel sources of 2.4.20-rc4-ac1_.
It might be that my patch is wrong but there's undoubtable something
that needs to be fixed.
> M.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2002-11-29 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 19:01 Linux 2.4.20-rc4-ac1 Alan Cox
2002-11-28 0:21 ` Adrian Bunk
2002-11-28 13:01 ` Adrian Bunk
2002-11-28 16:15 ` Martin J. Bligh
2002-11-29 16:16 ` Adrian Bunk [this message]
2002-11-28 13:43 ` Adrian Bunk
2002-11-28 14:05 ` Francois Romieu
2002-11-28 20:52 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 17:01 Margit Schubert-While
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=20021129161633.GG6981@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=alan@redhat.com \
--cc=johnstul@us.ibm.com \
--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.