public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: Andi Kleen <ak@muc.de>
Cc: "Michael Chan" <mchan@broadcom.com>, linux-kernel@vger.kernel.org
Subject: Re: MMCONFIG violates pci power mgmt spec
Date: Thu, 05 Aug 2004 15:45:50 -0700	[thread overview]
Message-ID: <52pt65fbkx.fsf@topspin.com> (raw)
In-Reply-To: <m3brhp8biw.fsf@averell.firstfloor.org> (Andi Kleen's message of "Fri, 06 Aug 2004 00:28:55 +0200")

    Andi> If someone cites the spec that says that it is not allowed I
    Andi> guess it could be removed.

I believe the PCI Express spec says that config writes are never posted.
(I'll check later to be sure)

 - Roland

  reply	other threads:[~2004-08-05 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2pYrs-17y-31@gated-at.bofh.it>
2004-08-05 22:28 ` MMCONFIG violates pci power mgmt spec Andi Kleen
2004-08-05 22:45   ` Roland Dreier [this message]
2004-08-05 23:30 Michael Chan
  -- strict thread matches above, loose matches on Subject: below --
2004-08-05 23:22 Michael Chan
2004-08-05 21:50 Michael Chan

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=52pt65fbkx.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchan@broadcom.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