From: Andrew Morton <akpm@digeo.com>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: balance_dirty_pages broken
Date: Wed, 16 Oct 2002 23:09:25 -0700 [thread overview]
Message-ID: <3DAE5415.938EA547@digeo.com> (raw)
In-Reply-To: 20021017060123.GD10276@redhat.com
Doug Ledford wrote:
>
> On Wed, Oct 16, 2002 at 10:54:15PM -0700, Andrew Morton wrote:
> > Doug Ledford wrote:
> > >
> > > On Thu, Oct 17, 2002 at 01:22:46AM -0400, Doug Ledford wrote:
> > > > Sure, coming under separate cover.
> > >
> > > Actually, this isn't needed now I assume ;-)
> >
> > Well I was rather interested in seeing it to find out why your
> > compile is busted. You seem to be very protective of the compiler
> > error messages ;)
>
> OK. .config attached, error message inline:
>
> gcc -Wp,-MD,arch/i386/kernel/.mpparse.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=i686 -Iarch/i386/mach-generic -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=mpparse -c -o arch/i386/kernel/mpparse.o
> arch/i386/kernel/mpparse.c
> arch/i386/kernel/mpparse.c: In function `MP_processor_info':
> arch/i386/kernel/mpparse.c:130: warning: implicit declaration of function
> `Dprintk'
but, but, but. The patch I sent should have fixed that. It makes
Dprintk visible in apic.h regardless of the setting of CONFIG_X86_LOCAL_APIC
> ...
>
> Should I run another test of just this patch to be sure?
She'll be right, mate.
prev parent reply other threads:[~2002-10-17 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 4:36 balance_dirty_pages broken Doug Ledford
2002-10-17 5:09 ` Andrew Morton
2002-10-17 5:22 ` Doug Ledford
2002-10-17 5:41 ` Doug Ledford
2002-10-17 5:54 ` Andrew Morton
2002-10-17 6:01 ` Doug Ledford
2002-10-17 6:09 ` Andrew Morton [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=3DAE5415.938EA547@digeo.com \
--to=akpm@digeo.com \
--cc=dledford@redhat.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.