From: Andrew Morton <akpm@linux-foundation.org>
To: Yinghai Lu <Yinghai.Lu@Sun.COM>
Cc: Andi Kleen <ak@suse.de>, Jeff Garzik <jeff@garzik.org>,
Greg KH <greg@kroah.com>, Martin Mares <mj@ucw.cz>,
dean gaudet <dean@arctic.org>,
Robert Richter <robert.richter@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used
Date: Wed, 12 Sep 2007 19:17:39 -0700 [thread overview]
Message-ID: <20070912191739.fc0e2554.akpm@linux-foundation.org> (raw)
In-Reply-To: <200709121921.43950.yinghai.lu@sun.com>
On Wed, 12 Sep 2007 19:21:43 -0700 Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
> +/**
> + * Regular PCI devices have 256 bytes, but AMD Family 10h Opteron ext config
> + * have 4096 bytes. Even if the device is capable, that doesn't mean we can
> + * access it. Maybe we don't have a way to generate extended config space
> + * accesses. So check it
> + */
Please don't use the kerneldoc leadin "/**" for non-kerneldoc comments.
next prev parent reply other threads:[~2007-09-13 2:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 2:21 [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used Yinghai Lu
2007-09-13 2:17 ` Andrew Morton [this message]
2007-09-13 9:47 ` Andi Kleen
2007-09-13 10:47 ` Greg KH
2007-09-13 11:53 ` Andi Kleen
2007-09-13 17:01 ` Yinghai Lu
2007-09-13 17:20 ` H. Peter Anvin
2007-09-13 19:22 ` Yinghai Lu
2007-09-13 19:31 ` H. Peter Anvin
2007-09-13 20:15 ` Andreas Herrmann
2007-09-13 20:54 ` H. Peter Anvin
2007-09-14 11:21 ` [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG Andreas Herrmann
2007-09-14 14:08 ` H. Peter Anvin
2007-09-14 17:28 ` Yinghai Lu
2007-09-14 18:09 ` Yinghai Lu
2007-09-16 3:18 ` [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used Andi Kleen
2007-09-13 19:52 ` Andreas Herrmann
2007-09-13 20:14 ` Yinghai Lu
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=20070912191739.fc0e2554.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Yinghai.Lu@Sun.COM \
--cc=ak@suse.de \
--cc=dean@arctic.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=robert.richter@amd.com \
/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