From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Simon Kågström" <simon.kagstrom@netinsight.net>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Small request for patch review in DPDK
Date: Wed, 27 May 2015 14:39:57 +0000 [thread overview]
Message-ID: <D18B4136.20FD9%keith.wiles@intel.com> (raw)
In-Reply-To: <55655D3D.8070208@netinsight.net>
On 5/27/15, 12:59 AM, "Simon Kågström" <simon.kagstrom@netinsight.net>
wrote:
>Hi!
>
>As a well-meaning outsider submitting small patches to DPDK, I'd very
>much appreciate help from the community with review and comments. Since
>I'm a DPDK newbie, the patches might be incorrect or wrong in some other
>way, so I think it's even more important with reviews for people like me.
>
>But I can't help getting this nagging feeling that the patches are
>actually lost in the flood of mail to the DPDK mailing list, since I
>haven't gotten any reaction to any of the three patches I've sent the
>last month.
>
>
>The patches in question are
>
> kni: Add set_rx_mode callback to handle multicast groups
> rte_reorder: Allow sequence numbers > 0 as starting point
> eal_common_options: Allow combining -m and --no-huge
>
>so if someone feels like mining their DPDK mail box, please review if
>you have the time and knowledge about the area :-)
>
>
>And I can't help thinking that maybe github pull requests would be
>harder to miss (or at least easier to find after a few weeks of other
>traffic).
Do not open that can of worms :-) But I agree with you.
>
>// Simon
prev parent reply other threads:[~2015-05-27 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 5:59 Small request for patch review in DPDK Simon Kågström
2015-05-27 14:39 ` Wiles, Keith [this message]
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=D18B4136.20FD9%keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=simon.kagstrom@netinsight.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.