From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"yipeng1.wang@intel.com" <yipeng1.wang@intel.com>,
Dharmik Thakkar <Dharmik.Thakkar@arm.com>,
"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v6 0/5] Address reader-writer concurrency in rte_hash
Date: Fri, 26 Oct 2018 00:48:48 +0000 [thread overview]
Message-ID: <AM6PR08MB36729077EEFC238BCDF255A198F00@AM6PR08MB3672.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <2478359.0TPsiFennH@xps>
>
> 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@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@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@example.com'.
Then section 5.7.2 says that 'all fix patches to the master that are candidates for backporting should have 'Cc:stable@dpdk.org' and should be CCed to stable@dpdk.org mailing list.
Last time I CCed a patch to stable@dpdk.org, I was told not to do it, 'Cc:stable@dpdk.org' in the commit message is enough.
Any clarification would help.
>
next prev parent reply other threads:[~2018-10-26 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 1:32 Honnappa Nagarahalli
2018-10-24 1:32 ` [dpdk-dev] [PATCH v6 1/5] hash: separate multi-writer from rw-concurrency Honnappa Nagarahalli
2018-10-24 1:32 ` [dpdk-dev] [PATCH v6 2/5] hash: support do not free on delete Honnappa Nagarahalli
2018-10-25 22:55 ` Thomas Monjalon
2018-10-26 1:20 ` Honnappa Nagarahalli
2018-10-24 1:32 ` [dpdk-dev] [PATCH v6 3/5] hash: fix key store element alignment Honnappa Nagarahalli
2018-10-24 1:32 ` [dpdk-dev] [PATCH v6 4/5] hash: add lock-free read-write concurrency Honnappa Nagarahalli
2018-10-24 1:32 ` [dpdk-dev] [PATCH v6 5/5] test/hash: read-write lock-free concurrency test Honnappa Nagarahalli
2018-10-25 22:56 ` [dpdk-dev] [PATCH v6 0/5] Address reader-writer concurrency in rte_hash Thomas Monjalon
2018-10-26 0:48 ` Honnappa Nagarahalli [this message]
2018-10-26 8:38 ` Thomas Monjalon
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=AM6PR08MB36729077EEFC238BCDF255A198F00@AM6PR08MB3672.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Dharmik.Thakkar@arm.com \
--cc=Gavin.Hu@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas@monjalon.net \
--cc=yipeng1.wang@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).