From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Thomas Monjalon
<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] pci: fix non-Intel devices probing
Date: Mon, 16 Sep 2013 16:59:33 -0700 [thread overview]
Message-ID: <20130916165933.2421a45e@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1570236.KP93u3nrzz@x220>
I agree with Thomas, the check is not needed.
After this all settles out, I have a patch to add support for I/O
resource tracking in base DPDK. It makes it easier to do the right
thing in drivers that need to use I/O instead of memory.
next prev parent reply other threads:[~2013-09-16 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 20:29 [PATCH] pci: fix non-Intel devices probing Thomas Monjalon
[not found] ` <1379363340-20870-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-09-16 20:38 ` Thomas Monjalon
2013-09-16 21:42 ` Patrick Mahan
[not found] ` <BBFDF6C2-16DE-413B-8A68-DA85A68774DE-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-09-16 21:59 ` Thomas Monjalon
2013-09-16 23:59 ` Stephen Hemminger [this message]
2013-09-17 10:21 ` [PATCH v2 0/2] " Thomas Monjalon
[not found] ` <cover.1379413101.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-09-17 10:21 ` [PATCH v2 1/2] pci: do not check BAR0 mapping Thomas Monjalon
[not found] ` <6d68788d4315a3c2e13e244b0658429334df2572.1379413101.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-09-17 11:26 ` Damien Millescamps
2013-09-17 10:21 ` [PATCH v2 2/2] pci: use igb_uio mapping only when needed Thomas Monjalon
[not found] ` <82132fea875815a5569d5138b2531eabf6545090.1379413101.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-09-17 11:27 ` Damien Millescamps
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=20130916165933.2421a45e@nehalam.linuxnetplumber.net \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).