linux-kernel - Re: [PATCH 1/2] driver core: remove device_add

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130319001822.GC13502@kroah.com>
Date:	Mon, 18 Mar 2013 17:18:22 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Wei Yang <weiyang@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, joe@...ches.com,
	shangw@...ux.vnet.ibm.com, linuxram@...ibm.com
Subject: Re: [PATCH 1/2] driver core: remove device_add_attrs() in
 drivers/base/bus.c

On Thu, Mar 07, 2013 at 10:22:45AM +0800, Wei Yang wrote:
> Originally, we have two functions named device_add_attrs() in
> drivers/base/bus.c and drivers/base/core.c. This will cause some confusion
> when reading the code.

Why?  It's just static functions.

> And the one in drivers/base/bus.c do the same action as device_add_attributes()
> in drivers/base/core.c. That would be better to reuse this code.

Possibly, yes, but you put the .h entry in the wrong place, thereby
exposing a previously static function to the entire kernel, which is not
good at all.  Why did you do that?  Are you now going to want to call
that function from some driver?

greg k-h
--
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/