DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: jigsaw <jigsaw@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] Add in_flight_bitmask so as to use full 32 bits of tag.
Date: Thu, 13 Nov 2014 10:18:36 +0100	[thread overview]
Message-ID: <1790564.eeil24UKmd@xps13> (raw)
In-Reply-To: <CAHVfvh6zLy8pGyuWw5QTKowxoZWgSH2-TpOYEVO-RXqsM9-rdQ@mail.gmail.com>

2014-11-13 08:56, jigsaw:
> >>Do you have another commit before this one in your tree?
> 
> Yes this patch relies on this one:
> http://dpdk.org/ml/archives/dev/2014-November/007943.html
> 
> Sorry I didn't make it clear. The new field usr in rte_mbuf was under same
> cover letter in v2 of the in_flight_bitmask patch.
> Then in_flight_bitmask has a v3 patch, but I didn't include the rte_mbuf in
> the same cover letter, coz the usr patch has been ACKed.

OK. In this case, you should re-submit the whole serie and add the acked-by
line in the patch, and/or use the --in-reply-to option to place the v3 patch in
the original thread.

No need to resend it, I can manage to get the whole patchset now.

Thanks
-- 
Thomas

  reply	other threads:[~2014-11-13  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 14:44 Qinglai Xiao
2014-11-10 15:13 ` Bruce Richardson
2014-11-10 15:52   ` jigsaw
2014-11-10 16:55     ` Bruce Richardson
2014-11-11  8:53       ` jigsaw
2014-11-12 15:51         ` Bruce Richardson
2014-11-13 11:26           ` Thomas Monjalon
2014-11-13  0:50 ` Thomas Monjalon
2014-11-13  6:56   ` jigsaw
2014-11-13  9:18     ` Thomas Monjalon [this message]
2014-11-13  9:24       ` jigsaw

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=1790564.eeil24UKmd@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jigsaw@gmail.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).