From: Thomas Monjalon <thomas@monjalon.net>
To: Bernard Iremonger <bernard.iremonger@intel.com>
Cc: stable@dpdk.org, qabuild@intel.com
Subject: Re: [dpdk-stable] [DPDK 1/2] examples/ipsec-secgw: fix 1st pkt dropped for inline crypto
Date: Wed, 10 Jul 2019 14:58:39 +0200 [thread overview]
Message-ID: <9324777.qQXKiXinF4@xps> (raw)
In-Reply-To: <1562756263-29712-1-git-send-email-bernard.iremonger@intel.com>
Is this patch intended to be sent to stable@dpdk.org?
If yes, dev@dpdk.org is missing.
If no, you should disable the automatic Cc with something like
--suppress-cc=bodycc
next prev parent reply other threads:[~2019-07-10 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 10:57 Bernard Iremonger
2019-07-10 10:57 ` [dpdk-stable] [DPDK 2/2] examples/ipsec-secgw/test: fix inline test scripts Bernard Iremonger
2019-07-10 12:58 ` Thomas Monjalon [this message]
2019-07-10 13:32 ` [dpdk-stable] [DPDK 1/2] examples/ipsec-secgw: fix 1st pkt dropped for inline crypto Iremonger, Bernard
-- strict thread matches above, loose matches on Subject: below --
2019-07-10 12:49 Bernard Iremonger
2019-06-12 14:19 Bernard Iremonger
2019-06-06 11:00 Bernard Iremonger
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=9324777.qQXKiXinF4@xps \
--to=thomas@monjalon.net \
--cc=bernard.iremonger@intel.com \
--cc=qabuild@intel.com \
--cc=stable@dpdk.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).