From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] make a couple eth_dev_ops const
Date: Fri, 13 Jan 2017 16:38:56 +0100 [thread overview]
Message-ID: <1859631.d3X9H1Gb87@xps13> (raw)
In-Reply-To: <088c65d6-e709-23dd-3a86-e90e192fd30f@intel.com>
2017-01-12 21:54, Ferruh Yigit:
> On 1/12/2017 7:12 PM, Stephen Hemminger wrote:
> > Really trivial patches.
>
> Patches are not in patchwork, and not in the mail list.
>
> > I also consider this a litmus test of how long it takes DPDK
> > project to merge trivial maintaince patches.
This is a nice example of why patches are not merged timely,
sometimes they are not received at all :)
In order to reduce the time needed to merge, could you please
run devtools/check-git-log.sh ?
next prev parent reply other threads:[~2017-01-13 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 19:12 Stephen Hemminger
2017-01-12 21:54 ` Ferruh Yigit
2017-01-13 15:38 ` Thomas Monjalon [this message]
2017-01-16 13:27 ` [dpdk-dev] [PATCH] net/bnxt: make eth dev ops struct const Ferruh Yigit
2017-01-16 13:27 ` [dpdk-dev] [PATCH] net/ena: " Ferruh Yigit
2017-01-16 13:44 ` [dpdk-dev] [PATCH] net/bnxt: " Ferruh Yigit
2017-01-17 20:57 ` Thomas Monjalon
2017-01-17 22:38 ` Stephen Hemminger
2017-01-18 12:01 ` Ferruh Yigit
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=1859631.d3X9H1Gb87@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).