From: "Naveen Jain" <naveen_jain@ti.com>
To: "Greg KH" <gregkh@suse.de>
Cc: <devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>,
"Savoy, Pavan" <pavan_savoy@ti.com>
Subject: Re: [PATCH] drivers:staging: ti-st: add version info to sysfs
Date: Wed, 9 Jun 2010 14:23:02 +0530 [thread overview]
Message-ID: <00b801cb07b1$2cce1420$LocalHost@MINX0100354> (raw)
In-Reply-To: 20100608150310.GA29618@suse.de
From: "Greg KH" <gregkh@suse.de>
To: "Jain, Naveen" <naveen_jain@ti.com>
Cc: <devel@driverdev.osuosl.org>; <linux-kernel@vger.kernel.org>; "Savoy,
Pavan" <pavan_savoy@ti.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@ti.com wrote:
>> From: Naveen Jain <naveen_jain@ti.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.
[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
next prev parent reply other threads:[~2010-06-09 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 14:54 [PATCH] drivers:staging: ti-st: add version info to sysfs naveen_jain
2010-06-08 15:03 ` Greg KH
2010-06-09 8:53 ` Naveen Jain [this message]
2010-06-09 15:20 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00b801cb07b1$2cce1420$LocalHost@MINX0100354' \
--to=naveen_jain@ti.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox