[dpdk-dev] [PATCH v2 1/6] examples/ipsec-secgw: fix initialization of aead crypto devices

[Thomas Monjalon]

22/10/2017 09:21, Aviad Yehezkel:
> On 10/20/2017 12:50 PM, De Lara Guarch, Pablo wrote:
> > From: aviadye at dev.mellanox.co.il
> >> From: Aviad Yehezkel <aviadye at mellanox.com>
> >>
> >> Fixes: 501e9c226adf ("examples/ipsec-secgw: add AEAD parameters")
> >> Cc: pablo.de.lara.guarch at intel.com
> > 
> > You should CC stable here.
> 
> You referred me to http://dpdk.org/doc/guides/contributing/patches.html
> I followed the documentation:
> "
> When fixing a regression, it is required to reference the id of the 
> commit which introduced the bug, and put the original author of that 
> commit on CC. Yiu can generate the required lines using the following 
> git alias, which print the commit SHA and the author of the original code:
> git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h 
> (\"%s\")%nCc: %ae'"
> "
> Please explain when to use above alias and when to put stable or 
> something else.

It seems it is not described in the chapter 5.
It is mentioned only in chapter 6:
	http://dpdk.org/doc/guides/contributing/stable.html#the-stable-mailing-list

But when running devtools/check-git-log.sh as described in chapter 5:
	http://dpdk.org/doc/guides/contributing/patches.html#checking-the-patches
You should see this:
	Is it candidate for Cc: stable at dpdk.org backport?
It is using devtools/git-log-fixes.sh to get patches which are fixing
older releases.

Short answer:
You must add "Cc: stable at dpdk.org" just below "Fixes:" if the bug
was introduced in an older release.
It will trigger the patch to be backported in maintenance releases.

It is the responsibility of the tree maintainer to check this tag,
and add or remove it, if he thinks the backport requirement was not
properly considered.