[dpdk-dev] [PATCH v6 0/5] Address reader-writer concurrency in rte_hash
Honnappa Nagarahalli
Honnappa.Nagarahalli at arm.com
Fri Oct 26 02:48:48 CEST 2018
>
> 24/10/2018 03:32, Honnappa Nagarahalli:
> > Dharmik Thakkar (1):
> > test/hash: read-write lock-free concurrency test
> >
> > Honnappa Nagarahalli (4):
> > hash: separate multi-writer from rw-concurrency
> > hash: support do not free on delete
> > hash: fix key store element alignment
> > hash: add lock-free read-write concurrency
>
> Please add Cc: stable at dpdk.org below Fixes: line when the fix must be
> backported.
>
> The script check-git-log.sh will help in this task.
I did not run this script, will run from next time.
I am confused about when to add 'stable at dpdk.org'.
https://doc.dpdk.org/guides-18.08/contributing/patches.html section 5.7 says that while fixing a 'regression' (any issue due to a previous code change), we should add 'author at example.com'.
Then section 5.7.2 says that 'all fix patches to the master that are candidates for backporting should have 'Cc:stable at dpdk.org' and should be CCed to stable at dpdk.org mailing list.
Last time I CCed a patch to stable at dpdk.org, I was told not to do it, 'Cc:stable at dpdk.org' in the commit message is enough.
Any clarification would help.
>
More information about the dev
mailing list