Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rongqing Li <rongqing.li@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH v2][meta-networking] tcpslice: add recipe under tcpdump
Date: Tue, 2 Sep 2014 10:45:16 +0800	[thread overview]
Message-ID: <54052F3C.6090006@windriver.com> (raw)
In-Reply-To: <20140730072555.GF16445@jama>



On 07/30/2014 03:25 PM, Martin Jansa wrote:
> On Wed, Jul 30, 2014 at 10:22:41AM +0800,rongqing.li@windriver.com  wrote:
>> >From: Roy Li<rongqing.li@windriver.com>
>> >
>> >tcpslice is a tool for extracting parts of a tcpdump packet trace,
>> >so put it under tcpdump dir
>> >
>> >Signed-off-by: Roy Li<rongqing.li@windriver.com>
>> >---


Hi Martin:

I see this recipes has been merged into master-next for a long time,
Could you cherry-pick it to master?


-Roy


-- 
Best Reagrds,
Roy | RongQing Li


  parent reply	other threads:[~2014-09-02  2:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  2:22 [PATCH v2][meta-networking] tcpslice: add recipe under tcpdump rongqing.li
2014-07-30  7:25 ` Martin Jansa
2014-07-30  7:29   ` Rongqing Li
2014-09-02  2:45   ` Rongqing Li [this message]
2014-09-02 12:19     ` Joe MacDonald
2014-09-03  0:44       ` Rongqing Li

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=54052F3C.6090006@windriver.com \
    --to=rongqing.li@windriver.com \
    --cc=openembedded-devel@lists.openembedded.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