linux-kernel - Re: [PATCH] rcu: Replace rcu_assign_pointer(x, NULL) with RCU_INIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20140319.163009.460997858507816239.davem@davemloft.net>
Date:	Wed, 19 Mar 2014 16:30:09 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	monamagarwal123@...il.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	eddie.wai@...adcom.com, paulmck@...ux.vnet.ibm.com
Subject: Re: [PATCH] rcu: Replace rcu_assign_pointer(x, NULL) with
 RCU_INIT_POINTER(x, NULL)


Many of your patches, such as this one, all have the same exact
subject line.

This makes it impossible to scan the subject lines and have some
idea what area a commit makes changes.

I would really suggest that you use a subject prefix that references
the driver or subsystem, so for this one:

Subject: [PATCH N/M] infiniband: Use rcu_assign_pointer(x, NULL instead) of RCU_INIT_POINTER(x, NULL)

and likewise for all of your other patches.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/