From: Greg KH <greg@kroah.com>
To: pavan_savoy@ti.com
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 2/7] drivers:misc: ti-st: move from rfkill to sysfs
Date: Thu, 3 Feb 2011 16:03:30 -0800 [thread overview]
Message-ID: <20110204000330.GA20634@kroah.com> (raw)
In-Reply-To: <1296644448-29667-3-git-send-email-pavan_savoy@ti.com>
On Wed, Feb 02, 2011 at 05:00:43AM -0600, pavan_savoy@ti.com wrote:
> From: Pavan Savoy <pavan_savoy@ti.com>
>
> The communication between ST KIM and UIM was interfaced
> over the /dev/rfkill device node.
> Move the interface to a simpler less abusive sysfs entry
> mechanism.
That's nice, but you need to document all sysfs files in
Documentation/ABI/
Can you please do that in this patch and resend the series?
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-04 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 11:00 [PATCH 0/7] TI ST patches for new requirements pavan_savoy
2011-02-02 11:00 ` [PATCH 1/7] drivers:misc: ti-st: register with channel IDs pavan_savoy
2011-02-02 11:00 ` [PATCH 2/7] drivers:misc: ti-st: move from rfkill to sysfs pavan_savoy
2011-02-02 11:00 ` [PATCH 3/7] drivers:misc: ti-st: fix error codes pavan_savoy
2011-02-02 11:00 ` [PATCH 4/7] drivers:misc: ti-st: set right debug levels for logs pavan_savoy
2011-02-02 11:00 ` [PATCH 5/7] drivers:misc: ti-st: firmware download optimization pavan_savoy
2011-02-02 11:00 ` [PATCH 6/7] drivers:misc: ti-st: fix hci-ll on wake_ind collision pavan_savoy
2011-02-02 11:00 ` [PATCH 7/7] drivers:misc: ti-st: remove multiple gpio handling pavan_savoy
2011-02-04 0:03 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 8:23 [PATCH 0/7] TI ST patches for new requirements pavan_savoy
2011-02-04 8:23 ` [PATCH 1/7] drivers:misc: ti-st: register with channel IDs pavan_savoy
2011-02-04 8:23 ` [PATCH 2/7] drivers:misc: ti-st: move from rfkill to sysfs pavan_savoy
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=20110204000330.GA20634@kroah.com \
--to=greg@kroah.com \
--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