From: Tony Camuso <tcamuso@redhat.com>
To: gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: [Fwd: Re: [PATCH 1/5]PCI: x86 MMCONFIG: introduce PCI_USING_MMCONF]
Date: Thu, 20 Dec 2007 07:23:11 -0500 [thread overview]
Message-ID: <476A5EAF.6020008@redhat.com> (raw)
To all,
The next few forwarded messages comprise my responses to Greg's
questions about the patch I submitted to deal with pci devices
that do not respond correctly to x86 mmconf accesses.
Please accept my apologies for not having including the community
in my original responses.
-------- Original Message --------
Subject: Re: [PATCH 1/5]PCI: x86 MMCONFIG: introduce PCI_USING_MMCONF
Date: Wed, 19 Dec 2007 18:58:45 -0500
From: Tony Camuso <tcamuso@redhat.com>
Reply-To: tcamuso@redhat.com
To: Greg KH <gregkh@suse.de>
References:
<20071219221746.20362.39243.sendpatchset@dhcp83-188.boston.redhat.com>
<20071219221751.20362.23451.sendpatchset@dhcp83-188.boston.redhat.com>
<20071219230447.GA24219@suse.de>
Greg KH wrote:
> On Wed, Dec 19, 2007 at 05:17:51PM -0500, tcamuso@redhat.com wrote:
>>
>> +extern struct pci_ops pci_legacy_ops; /* direct.c */
>
> This isn't needed in this patch at all, and might make the compiler
> confused if you were to build with only this patch present :(
>
> thanks,
>
> greg k-h
Yes, of course. I missed that. Thank you.
Should I resubmit that one patch? Or would you prefer I resubmit
the whole patch set?
next reply other threads:[~2007-12-20 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 12:23 Tony Camuso [this message]
2007-12-20 14:19 ` [Fwd: Re: [PATCH 1/5]PCI: x86 MMCONFIG: introduce PCI_USING_MMCONF] Tony Camuso
2007-12-20 16:48 ` Greg KH
2007-12-20 17:00 ` Tony Camuso
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=476A5EAF.6020008@redhat.com \
--to=tcamuso@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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.