All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPI Compile error in current git (pci.h)
Date: Thu, 6 Apr 2006 14:09:12 +1000	[thread overview]
Message-ID: <200604061409.16581.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060406035012.GB26601@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Hi Greg.

On Thursday 06 April 2006 13:50, Greg KH wrote:
> On Fri, Mar 24, 2006 at 02:37:18PM +1000, Nigel Cunningham wrote:
> > Hi again.
> >
> > On Friday 24 March 2006 14:04, Nigel Cunningham wrote:
> > > Hi.
> > >
> > > Current git produces the following compile error (x86_64 uniprocessor
> > > compile):
> > >
> > > arch/x86_64/pci/mmconfig.c:152: error: conflicting types for
> > > ???pci_mmcfg_init??? arch/i386/pci/pci.h:85: error: previous
> > > declaration of ???pci_mmcfg_init??? was here make[1]: ***
> > > [arch/x86_64/pci/mmconfig.o] Error 1 make: *** [arch/x86_64/pci] Error
> > > 2
> > >
> > > I haven't found out yet how the i386 file is getting included, but I
> > > can say that git compiled fine last night.
> >
> > Got the answer to this bit - it is included via the Makefile in the
> > directory setting a -I flag, and the file including "pci.h".
>
> Does this still happen for 2.6.17-rc1?
>
> thanks,
>
> greg k-h

No, it's fixed. I figured out the cause a little later the same day, and so 
did someone else (don't recall the name now). A patch has been merged.

Regards,

Nigel

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-04-06  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  4:04 ACPI Compile error in current git (pci.h) Nigel Cunningham
2006-03-24  4:37 ` Nigel Cunningham
2006-04-06  3:50   ` Greg KH
2006-04-06  4:09     ` Nigel Cunningham [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=200604061409.16581.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=gregkh@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --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.