From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v6 0/5] Address reader-writer concurrency in rte_hash Date: Fri, 26 Oct 2018 10:38:14 +0200 Message-ID: <7557349.NbPZBPCVeV@xps> References: <1540344746-29045-1-git-send-email-honnappa.nagarahalli@arm.com> <2478359.0TPsiFennH@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "dev@dpdk.org" , "bruce.richardson@intel.com" , "pablo.de.lara.guarch@intel.com" , "yipeng1.wang@intel.com" , Dharmik Thakkar , "Gavin Hu (Arm Technology China)" , nd To: Honnappa Nagarahalli Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id D023858C4 for ; Fri, 26 Oct 2018 10:38:12 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 26/10/2018 02:48, Honnappa Nagarahalli: > > > > 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. If you add Cc: stable@dpdk.org in the commit, git-send-email will automatically Cc the email. So the email will be sent to dev and stable at the same time. It's what should happen :)