From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Liu, KevinX" <kevinx.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Yuying" <yuying.zhang@intel.com>,
"Liu, KevinX" <kevinx.liu@intel.com>
Subject: RE: [PATCH] doc: fix missing title underline
Date: Tue, 5 Jul 2022 03:50:35 +0000 [thread overview]
Message-ID: <DM4PR11MB59941A5EA1354AD3783A10EAD7819@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220705104140.104619-1-kevinx.liu@intel.com>
> -----Original Message-----
> From: Kevin Liu <kevinx.liu@intel.com>
> Sent: Tuesday, July 5, 2022 6:42 PM
> To: dev@dpdk.org
> Cc: Xing, Beilei <beilei.xing@intel.com>; Zhang, Yuying
> <yuying.zhang@intel.com>; Liu, KevinX <kevinx.liu@intel.com>
> Subject: [PATCH] doc: fix missing title underline
>
> Title underline too short. Fill title underline.
>
> Fixes: ae97b8b89826 ("net/i40e: fix error disable double VLAN")
The patch has been squashed to above commit in dpdk-next-net-intel.
prev parent reply other threads:[~2022-07-05 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 10:41 Kevin Liu
2022-07-05 3:50 ` Zhang, Qi Z [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=DM4PR11MB59941A5EA1354AD3783A10EAD7819@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=kevinx.liu@intel.com \
--cc=yuying.zhang@intel.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).