From: Tomas Winkler <tomas.winkler@intel.com>
To: gregkh@linuxfoundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: [char-misc-next 0/5] MEI: move mei-me to separate module
Date: Wed, 27 Mar 2013 16:58:25 +0200 [thread overview]
Message-ID: <1364396310-10718-1-git-send-email-tomas.winkler@intel.com> (raw)
This completes the separation of the me hardware form mei
layer to give space for adding another underlying hardware
ME hardware is now encapsulated into mei-me module.
Tomas Winkler (5):
mei: unregister watchdog from mei_stop function
mei: ME structures should be initialized in mei_device_init
mei: rename function mei_hw_init to mei_start
mei: prefix me hardware specific functions with mei_me_
mei: move mei-me to separate module
drivers/misc/mei/Kconfig | 5 ++---
drivers/misc/mei/Makefile | 6 ++++--
drivers/misc/mei/hw-me.c | 44 ++++++++++++++++++--------------------------
drivers/misc/mei/init.c | 21 ++++++++++++++++++---
drivers/misc/mei/interrupt.c | 4 ++++
drivers/misc/mei/main.c | 4 ++++
drivers/misc/mei/mei_dev.h | 2 +-
drivers/misc/mei/pci-me.c | 40 +++++++++++++++++++---------------------
8 files changed, 70 insertions(+), 56 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-03-27 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 14:58 Tomas Winkler [this message]
2013-03-27 14:58 ` [char-misc-next 1/5] mei: unregister watchdog from mei_stop function Tomas Winkler
2013-03-27 14:58 ` [char-misc-next 2/5] mei: ME structures should be initialized in mei_device_init Tomas Winkler
2013-03-27 14:58 ` [char-misc-next 3/5] mei: rename function mei_hw_init to mei_start Tomas Winkler
2013-03-27 14:58 ` [char-misc-next 4/5] mei: prefix me hardware specific functions with mei_me_ Tomas Winkler
2013-03-27 14:58 ` [char-misc-next 5/5] mei: move mei-me to separate module 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=1364396310-10718-1-git-send-email-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®