From: Stephen Hemminger <stephen@networkplumber.org>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
"olaf@aepfle.de" <olaf@aepfle.de>,
linux-pci@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain
Date: Thu, 25 May 2017 08:52:08 -0700 [thread overview]
Message-ID: <20170525082215.4736027d@xeon-e3> (raw)
In-Reply-To: <20170525141955.6cee8fbb@alans-desktop>
On Thu, 25 May 2017 14:19:55 +0100
Alan Cox <gnomes@lxorguk.ukuu.org.uk> wrote:
> > > Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> > > ---
> >
> > According to Stephen Hemminger <sthemmin@microsoft.com>, there are
> > additional programs, like X.org, DPDK, are also using 16-bit only
> > PCI domain numbers. So, I'm submitting this patch for re-consideration.
>
> The correct way to handle this is to send the needed patches to DPDK and
> to X.org both of whom will I am sure be delighted to get it fixed in
> their codebase.
Both projects have stable ABI requirements. And the lead time to get
the change propagated out to applications is long (>5yrs) even longer
with the Enterprise distro's. As developers we can all just pass the
buck but this doesn't help users in any reasonable time fram. It is not
as simple as just making a patch or pull request for their upstream
code bases.
next prev parent reply other threads:[~2017-05-25 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 20:39 [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain Haiyang Zhang
2017-05-24 20:43 ` Haiyang Zhang
[not found] ` <20170525141955.6cee8fbb@alans-desktop>
2017-05-25 15:52 ` Stephen Hemminger [this message]
2017-05-25 7:56 ` Christoph Hellwig
2017-06-19 21:07 ` Bjorn Helgaas
2017-06-19 21:10 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2017-04-20 16:35 Haiyang Zhang
2017-04-20 18:33 ` Bjorn Helgaas
2017-04-20 18:37 ` Haiyang Zhang
2017-04-20 19:12 ` Christoph Hellwig
2017-04-24 23:06 ` John Hubbard
2017-04-25 13:00 ` Dan Carpenter
2017-04-25 13:14 ` Christoph Hellwig
2017-04-25 18:19 ` John Hubbard
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=20170525082215.4736027d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olaf@aepfle.de \
/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;
as well as URLs for NNTP newsgroup(s).