All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: "David Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH][BNX2]: Disable MSI on 5706 if AMD 8132 bridge is present
Date: Fri, 29 Sep 2006 16:27:35 -0700	[thread overview]
Message-ID: <1159572456.3741.38.camel@rh4> (raw)
In-Reply-To: <451DA902.7030409@garzik.org>

On Fri, 2006-09-29 at 19:15 -0400, Jeff Garzik wrote:

> It was completely vague as to why this incompatibility was specific to 
> the 5706, when -- as the description noted -- the behavior is legal.
> 

The description is a bit vague in that one aspect that Jeff pointed out,
but otherwise very complete in my opinion.

> Re-read the patch.  At no time does it say 5706 was in the wrong.
> 

The behavior is legal but AMD believes that it is unique to the 5706.  I
cannot make this less vague since it is a recommendation from AMD.  I
just trust their opinion on this.



  reply	other threads:[~2006-09-29 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 21:07 [PATCH][BNX2]: Disable MSI on 5706 if AMD 8132 bridge is present Michael Chan
2006-09-29 21:28 ` Jeff Garzik
2006-09-29 21:39   ` Michael Chan
2006-09-29 22:49     ` David Miller
2006-09-29 23:00       ` Jeff Garzik
2006-09-29 23:08         ` David Miller
2006-09-29 23:15           ` Jeff Garzik
2006-09-29 23:27             ` Michael Chan [this message]
2006-09-29 23:29             ` David Miller
2006-09-30  0:38               ` Jeff Garzik
2006-09-30  1:22                 ` David Miller
2006-09-29 23:46           ` Rick Jones
2006-09-30  0:16         ` Roland Dreier
2006-09-30  0:07 ` David Miller
2006-09-30 10:13 ` Brice Goglin
2006-09-30 18:09   ` 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=1159572456.3741.38.camel@rh4 \
    --to=mchan@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=netdev@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.