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
| ||
|
Date: Thu, 27 Sep 2012 21:37:50 -0400 From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> To: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com> Cc: wency@...fujitsu.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org, rientjes@...gle.com, liuj97@...il.com, len.brown@...el.com, benh@...nel.crashing.org, paulus@...ba.org, minchan.kim@...il.com, akpm@...ux-foundation.org Subject: Re: [PATCH 2/4] memory-hotplug: add node_device_release >> Moreover, your explanation is still insufficient. Even if >> node_device_release() is empty function, we can get rid of the >> warning. > > > I don't understand it. How can we get rid of the warning? See cpu_device_release() for example. >> Why do we need this node_device_release() implementation? > > I think that this is a manner of releasing object related kobject. No. Usually we never call memset() from release callback. -- 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/
Powered by blists - more mailing lists