From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
Date: Mon, 07 Aug 2017 14:14:48 -0700 (PDT) [thread overview]
Message-ID: <20170807.141448.1388035794329323595.davem@davemloft.net> (raw)
In-Reply-To: <588b378c-249a-36b0-8890-769258fbb708@huawei.com>
From: Ding Tianhong <dingtianhong@huawei.com>
Date: Mon, 7 Aug 2017 12:13:17 +0800
> Hi David?
>
> I think networking tree merge it is a better choice, as it mainly used to tell the NIC
> drivers how to use the Relaxed Ordering Attribute, and later we need send patch to enable
> RO for ixgbe driver base on this patch. But I am not sure whether Bjorn has some of his own
> view. :)
>
> Hi Bjorn:
>
> Could you help review this patch or give some feedback ?
I'm still waiting on this...
Bjorn?
next prev parent reply other threads:[~2017-08-07 21:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 7:15 [PATCH v9 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag Ding Tianhong
2017-08-05 7:15 ` [PATCH v9 1/4] PCI: Add new PCIe Fabric End Node flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING Ding Tianhong
2017-08-08 23:22 ` Bjorn Helgaas
2017-08-09 1:40 ` Casey Leedom
2017-08-09 3:02 ` Bjorn Helgaas
2017-08-09 12:17 ` Ding Tianhong
2017-08-09 16:36 ` Casey Leedom
2017-08-09 15:58 ` Raj, Ashok
2017-08-09 16:46 ` Casey Leedom
2017-08-09 18:00 ` Raj, Ashok
2017-08-09 20:11 ` Casey Leedom
2017-08-05 7:15 ` [PATCH v9 2/4] PCI: Disable PCIe Relaxed Ordering if unsupported Ding Tianhong
2017-08-09 2:22 ` Bjorn Helgaas
2017-08-09 3:25 ` Bjorn Helgaas
2017-08-09 13:42 ` Ding Tianhong
2017-08-09 12:33 ` Casey Leedom
2017-08-09 13:23 ` Ding Tianhong
2017-08-05 7:15 ` [PATCH v9 3/4] net/cxgb4: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag Ding Tianhong
2017-08-05 7:15 ` [PATCH v9 4/4] net/cxgb4vf: " Ding Tianhong
2017-08-07 3:47 ` [PATCH v9 0/4] Add " David Miller
2017-08-07 4:13 ` Ding Tianhong
2017-08-07 21:14 ` David Miller [this message]
2017-08-08 1:56 ` Bjorn Helgaas
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=20170807.141448.1388035794329323595.davem@davemloft.net \
--to=davem@davemloft.net \
--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