From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: RE: [PATCH] add release note for 21.11
Date: Fri, 11 Feb 2022 14:10:04 +0000 [thread overview]
Message-ID: <0b634a0f48a74ab3b5c94f0420b54274@intel.com> (raw)
In-Reply-To: <20220210193617.583127-1-lijuan.tu@intel.com>
> -----Original Message-----
> From: Tu, Lijuan <lijuan.tu@intel.com>
> Sent: 2022年2月11日 3:36
> To: ohilyard@iol.unh.edu
> Cc: dts@dpdk.org; Tu, Lijuan <lijuan.tu@intel.com>
> Subject: [PATCH] add release note for 21.11
>
> Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
Applied
prev parent reply other threads:[~2022-02-11 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 19:36 Lijuan Tu
2022-02-10 20:42 ` Owen Hilyard
2022-02-11 14:10 ` Tu, Lijuan [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=0b634a0f48a74ab3b5c94f0420b54274@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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).