From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] eal: uio irq fixes and enhancements
Date: Tue, 12 May 2015 22:02:20 +0200 [thread overview]
Message-ID: <10038698.H9HDUp8o5h@xps13> (raw)
In-Reply-To: <1430239000-30881-1-git-send-email-stephen@networkplumber.org>
2015-04-28 09:36, Stephen Hemminger:
> This set of patches starts out with fixing a regression where
> uio_pci_generic broke link state interrupt, then adds better
> management of PCI config space.
>
> Will leave up to document writers to update various release
> notes and API manuals as they see fit.
>
> Also, needs what ever shared library map file updates which
> maybe required when using dynamic libraries. But that should
> not stop acceptance of this patch set.
No, an incomplete patch cannot be accepted.
There are several solutions:
- Siobhan and Neil accept to work on doc and .map file
- You provide a good v2
- Someone else finish this patchset
- The bug remains (not a solution)
next prev parent reply other threads:[~2015-05-12 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 16:36 Stephen Hemminger
2015-04-28 16:36 ` [dpdk-dev] [PATCH 1/3] uio: fix irq handling with igb_uio Stephen Hemminger
2015-04-30 16:27 ` Bruce Richardson
2015-05-13 9:31 ` Thomas Monjalon
2015-04-28 16:36 ` [dpdk-dev] [PATCH 2/3] pci: add ability to read/write config space Stephen Hemminger
2015-04-28 16:36 ` [dpdk-dev] [PATCH 3/3] eal: use pci_uio_read/write config to enable/disable INTX Stephen Hemminger
2015-05-12 20:02 ` Thomas Monjalon [this message]
2015-05-13 8:57 ` [dpdk-dev] [PATCH 0/3] eal: uio irq fixes and enhancements Bruce Richardson
2015-05-13 9:32 ` Thomas Monjalon
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=10038698.H9HDUp8o5h@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).