mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 02/15 V2] mei: bus: rename nfc.c to bus-fixup.c
Date: Mon, 15 Jun 2015 21:56:42 +0300	[thread overview]
Message-ID: <1434394615-3754-3-git-send-email-tomas.winkler@intel.com> (raw)
In-Reply-To: <1434394615-3754-1-git-send-email-tomas.winkler@intel.com>

The bus-fixup.c will be a place for fixups and quirks
for all types of me client devices.
As for now it contians only the fixup for setting
the nfc device name on the me client bus.

Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
---
 drivers/misc/mei/Makefile               | 2 +-
 drivers/misc/mei/{nfc.c => bus-fixup.c} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename drivers/misc/mei/{nfc.c => bus-fixup.c} (100%)

diff --git a/drivers/misc/mei/Makefile b/drivers/misc/mei/Makefile
index 518914a82b83..01447ca21c26 100644
--- a/drivers/misc/mei/Makefile
+++ b/drivers/misc/mei/Makefile
@@ -11,7 +11,7 @@ mei-objs += main.o
 mei-objs += amthif.o
 mei-objs += wd.o
 mei-objs += bus.o
-mei-objs += nfc.o
+mei-objs += bus-fixup.o
 mei-$(CONFIG_DEBUG_FS) += debugfs.o
 
 obj-$(CONFIG_INTEL_MEI_ME) += mei-me.o
diff --git a/drivers/misc/mei/nfc.c b/drivers/misc/mei/bus-fixup.c
similarity index 100%
rename from drivers/misc/mei/nfc.c
rename to drivers/misc/mei/bus-fixup.c
-- 
2.4.3


  parent reply	other threads:[~2015-06-15 19:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 18:56 [char-misc-next 00/15 V2] revamp mei bus Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 01/15 V2] mei: bus: fix drivers and devices names confusion Tomas Winkler
2015-07-23  4:30   ` Greg KH
2015-06-15 18:56 ` Tomas Winkler [this message]
2015-06-15 18:56 ` [char-misc-next 03/15 V2] mei: bus: move driver api functions at the start of the file Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 04/15] mei: bus: rename uevent handler to mei_cl_device_uevent Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 05/15 V2] mei: bus: don't enable events implicitly in device enable Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 06/15 V2] mei: bus: report if event registration failed Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 07/15 V2] mei: bus: revamp device matching Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 08/15 V2] mei: bus: revamp probe and remove functions Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 09/15 V2] mei: bus: add reference to bus device in struct mei_cl_client Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 10/15 V2] mei: bus: add me client device list infrastructure Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 11/15 V2] mei: bus: enable running fixup routines before device registration Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 12/15] mei: bus: blacklist the nfc info client Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 13/15] mei: bus: blacklist clients by number of connections Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 14/15 V2] mei: bus: simplify how we build nfc bus name Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 15/15 V2] mei: bus: link client devices instead of host clients 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=1434394615-3754-3-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®