From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: wenzhuo.lu@intel.com
Cc: dev@dpdk.org, Jiuling Bie <bie.jiuling@gmail.com>
Subject: Re: [dpdk-dev] Fwd: [PATCH] em: enable flash access, tested with Intel 82577LM
Date: Mon, 26 Oct 2015 17:01:29 +0100 [thread overview]
Message-ID: <4251428.1HCjpdq6dK@xps13> (raw)
In-Reply-To: <CA+JyDZRF=1yZnG9nFyQ0wtB3ApK8ufgun9vUvAEbnfxczOin2A@mail.gmail.com>
This patch does not comply with the DPDK rules.
But the needs deserved to be discussed with the e1000 maintainer.
Wenzhuo?
2015-10-07 13:27, Jiuling Bie:
> ---
> drivers/net/e1000/base/e1000_osdep.h | 18 ++++++++----------
> drivers/net/e1000/em_ethdev.c | 1 +
> lib/librte_eal/common/include/rte_pci_dev_ids.h | 1 +
> 3 files changed, 10 insertions(+), 10 deletions(-)
next prev parent reply other threads:[~2015-10-26 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444142686-2579-1-git-send-email-bie.jiuling@gmail.com>
2015-10-07 17:27 ` Jiuling Bie
2015-10-26 16:01 ` Thomas Monjalon [this message]
2015-10-27 1:01 ` Lu, Wenzhuo
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=4251428.1HCjpdq6dK@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bie.jiuling@gmail.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@intel.com \
/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).