linux-kernel - Re: [PATCH] drivers:staging: ti-st: add version info to sysfs

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]

Date:	Wed, 9 Jun 2010 08:20:21 -0700
From:	Greg KH <gregkh@...e.de>
To:	Naveen Jain <naveen_jain@...com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	"Savoy, Pavan" <pavan_savoy@...com>
Subject: Re: [PATCH] drivers:staging: ti-st: add version info to sysfs

On Wed, Jun 09, 2010 at 02:23:02PM +0530, Naveen Jain wrote:
> From: "Greg KH" <gregkh@...e.de>
> To: "Jain, Naveen" <naveen_jain@...com>
> Cc: <devel@...verdev.osuosl.org>; <linux-kernel@...r.kernel.org>;
> "Savoy, Pavan" <pavan_savoy@...com>
> Sent: Tuesday, June 08, 2010 8:33 PM
> Subject: Re: [PATCH] drivers:staging: ti-st: add version info to sysfs
> 
> 
> On Tue, Jun 08, 2010 at 09:54:45AM -0500, naveen_jain@...com wrote:
> >>From: Naveen Jain <naveen_jain@...com>
> >>
> >>Cleanup sysfs code, so that all the required sysfs entries
> >>are created under /sys/bus/platform/drivers/kim now.
> 
> >Where were they ending up?
> 
> Earlier the kobject was created under /sys/, and the entries went
> under /sys/uim. The below patch cleans that up.

Ick, for some reason I thought that was fixed up previously.

> [PATCH 1/2] drivers:staging: ti-st: cleanup sysfs code
> 
> 
> 
> >>Add version information to be available under the sysfs group
> >>for kim.
> 
> >How about splitting this into two different patches, as they do
> >different things?
> 
> It is split into two diff patches now.

Thanks.

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/