From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Ferruh Yigit'" <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] bug fixes for txgbe
Date: Fri, 5 Mar 2021 09:48:45 +0800 [thread overview]
Message-ID: <005501d71161$addc39f0$0994add0$@trustnetic.com> (raw)
In-Reply-To: <31e1f888-db8e-12b4-c4f3-d31ceed1ac3c@intel.com>
On Friday, March 5, 2021 12:49 AM, Ferruh Yigit wrote:
> On 3/4/2021 10:06 AM, Jiawen Wu wrote:
> > This series fix some bugs and remove unused functions.
> >
> > Jiawen Wu (4):
> > net/txgbe: remove unused functions
> > net/txgbe: fix Rx missed packet counter
> > net/txgbe: update packet type
> > net/txgbe: fix the process of adding crypto SA
> >
>
> Hi Jiawen,
>
> Can you please add fixes line for all of them?
> So that LTS maintainers can figure out where to backport the ones that can be
> backported.
>
> Fixes line is commit that introduces the issue fixed by that commit. It has a
> defined syntax which can be get via a git alias:
> git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h
> (\"%s\")%nCc: %ae'"
>
> (as documented in
> "https://doc.dpdk.org/guides/contributing/patches.html#commit-messages-bo
> dy")
Ok, I will add it.
Thanks for the guidance.
prev parent reply other threads:[~2021-03-05 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 10:06 Jiawen Wu
2021-03-04 10:06 ` [dpdk-dev] [PATCH 1/4] net/txgbe: remove unused functions Jiawen Wu
2021-03-04 10:06 ` [dpdk-dev] [PATCH 2/4] net/txgbe: fix Rx missed packet counter Jiawen Wu
2021-03-04 10:06 ` [dpdk-dev] [PATCH 3/4] net/txgbe: update packet type Jiawen Wu
2021-03-04 10:07 ` [dpdk-dev] [PATCH 4/4] net/txgbe: fix the process of adding crypto SA Jiawen Wu
2021-03-04 16:48 ` [dpdk-dev] [PATCH 0/4] bug fixes for txgbe Ferruh Yigit
2021-03-05 1:48 ` Jiawen Wu [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='005501d71161$addc39f0$0994add0$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).