From: Samuel Ortiz <sameo@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Tomas Winkler <tomas.winkler@intel.com>,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next 01/11 V4] mei: bus: Initial MEI Client bus type implementation
Date: Tue, 26 Mar 2013 23:01:37 +0100 [thread overview]
Message-ID: <20130326220137.GA32371@zurbaran> (raw)
In-Reply-To: <20130326133326.GA19511@zurbaran>
On Tue, Mar 26, 2013 at 02:33:26PM +0100, Samuel Ortiz wrote:
> On Mon, Mar 25, 2013 at 01:28:55PM -0700, Greg KH wrote:
> > On Thu, Mar 21, 2013 at 12:44:19AM +0200, Tomas Winkler wrote:
> > > create mode 100644 Documentation/misc-devices/mei/mei-client-bus.txt
> >
> > Shouldn't you also create Documentation/ABI/ entries as well?
> You mean for the bus specific stuff or for the /dev/mei entry ?
> For the bus parts, we're not adding any MEI specific sysfs entries. What
> should we document ?
I'm adding a modalias sysfs attribute, so I'll have to add an ABI
documentation entry for that.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-03-26 22:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 22:44 [char-misc-next 00/11 V4] Add Client MEI bus and NFC device Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 01/11 V4] mei: bus: Initial MEI Client bus type implementation Tomas Winkler
2013-03-25 20:28 ` Greg KH
2013-03-26 13:33 ` Samuel Ortiz
2013-03-26 22:01 ` Samuel Ortiz [this message]
2013-03-26 23:21 ` Greg KH
2013-03-20 22:44 ` [char-misc-next 02/11 V4] mei: bus: Implement driver registration Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 03/11 V4] mei: bus: Initial implementation for I/O routines Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 04/11 V4] mei: bus: Add bus related structures to mei_cl Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 05/11 V4] mei: bus: Call bus routines from the core code Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 06/11 V4] mei: bus: Synchronous API for the data transmission Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 07/11 V4] mei: bus: Implement bus driver data setter/getter Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 08/11 V4] mei: nfc: Initial nfc implementation Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 09/11 V4] mei: nfc: Connect also the regular ME client Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 10/11 V4] mei: nfc: Add NFC device to the MEI bus Tomas Winkler
2013-03-20 22:44 ` [char-misc-next 11/11 V4] mei: nfc: Implement MEI bus IO ops Tomas Winkler
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=20130326220137.GA32371@zurbaran \
--to=sameo@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.