From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [E1000-devel] ARM support for igb driver
Date: Sat, 31 May 2014 20:34:20 +0200 [thread overview]
Message-ID: <4893591.dl3XO76euB@wuerfel> (raw)
In-Reply-To: <CAHH3p5KdWvc_=m0XZxhb8drjpWVJ68BR_rH9bhrhNerSjCc-Tg@mail.gmail.com>
On Saturday 31 May 2014 01:44:28 shiv prakash Agarwal wrote:
> Notsure about root port, Can't it be disabled by Intel device?
My point is that it's the wrong place to disable it: every device
is allowed to generate this type of VDMs, and the root port is
supposed to silently ignore them if it doesn't handle them.
If the root port doesn't do that, it's a bug in the host bridge
driver, not in some device driver that happens to operate a
device within the specification.
Which host bridge driver do you use?
Arnd
next prev parent reply other threads:[~2014-05-31 18:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHH3p5KAwyMOY=ai_h0eM+JwYLtTO8d4jVaVOWVtOakhqPRTew@mail.gmail.com>
[not found] ` <CF7EA37A.4676A%matthew.vick@intel.com>
[not found] ` <CAHH3p5JFc3jgeK7OFd1rtgDS3gjRdjiPr3LwwqfyKMPGSTwMWA@mail.gmail.com>
[not found] ` <CF7FD060.46A87%matthew.vick@intel.com>
[not found] ` <CAHH3p5J8V6uWEzbCoT+x-6_2x1q=nc=_oMn0qnnj113FmeuW6A@mail.gmail.com>
[not found] ` <9B4A1B1917080E46B64F07F2989DADD6533627A5@ORSMSX114.amr.corp.intel.com>
[not found] ` <CAHH3p5KEPXw5mxP-13evd774nyO5C13ky0=fCaZPCNVx1gh3Ow@mail.gmail.com>
[not found] ` <CAHH3p5LaRwgdECxsO4OZSdWEhGt232yj-3347kYEStP6NLg2xg@mail.gmail.com>
[not found] ` <5360041A.7030005@intel.com>
[not found] ` <CAHH3p5L6WM3FaZ19Tw9vUcsk+kERfBKnGC2BRtnftJR1pbSF7g@mail.gmail.com>
2014-05-05 15:28 ` [E1000-devel] ARM support for igb driver Alexander Duyck
[not found] ` <CAHH3p5KEbvziVxg-9o45-chp=6U2JnW=ffk1p85GKFyWXiX8CQ@mail.gmail.com>
2014-05-05 20:00 ` Alexander Duyck
2014-05-05 20:38 ` Thomas Petazzoni
2014-05-05 21:20 ` Alexander Duyck
[not found] ` <CAHH3p5L4DaORYJ8_6zMEY3ikEnABU1L0B2C6Fezb_g6dCjtr5Q@mail.gmail.com>
2014-05-06 14:58 ` Alexander Duyck
2014-06-03 14:57 ` Ben Dooks
2014-05-06 15:18 ` Arnd Bergmann
2014-05-06 15:24 ` Lucas Stach
2014-05-06 15:33 ` Arnd Bergmann
2014-05-30 11:50 ` shiv prakash Agarwal
2014-05-30 17:21 ` Alexander Duyck
2014-05-30 18:02 ` shiv prakash Agarwal
2014-05-30 19:18 ` Jason Gunthorpe
2014-05-30 19:35 ` shiv prakash Agarwal
2014-05-30 19:56 ` Arnd Bergmann
2014-05-30 20:14 ` shiv prakash Agarwal
2014-05-30 21:11 ` Fujinaka, Todd
2014-05-31 18:34 ` Arnd Bergmann [this message]
2014-06-01 5:56 ` shiv prakash Agarwal
2014-06-01 11:46 ` Arnd Bergmann
2014-06-02 4:53 ` shiv prakash Agarwal
2014-06-02 16:05 ` Fujinaka, Todd
2014-06-03 12:33 ` shiv prakash Agarwal
2014-06-03 14:49 ` Ben Dooks
2014-06-03 15:05 ` Arnd Bergmann
2014-06-03 15:13 ` Ben Dooks
2014-06-03 15:23 ` Arnd Bergmann
2014-06-03 15:31 ` Ben Dooks
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=4893591.dl3XO76euB@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox