From: Sudeep Dutt <sudeep.dutt@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Nikhil Rao <nikhil.rao@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@intel.com>,
Harshavardhan R Kharche <harshavardhan.r.kharche@intel.com>,
"Yaozu (Eddie) Dong" <eddie.dong@intel.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Sudeep Dutt <sudeep.dutt@intel.com>
Subject: [PATCH CHAR-MISC-NEXT 0/4] Intel MIC Driver Cleanups.
Date: Thu, 26 Sep 2013 18:09:41 -0700 [thread overview]
Message-ID: <cover.1380241770.git.sudeep.dutt@intel.com> (raw)
These patches address code review feedback received on the patch
series @ https://lkml.org/lkml/2013/9/5/561 ,from:
a) Greg Kroah-Hartman on sysfs and header file cleanups.
b) Joe Perches on issues found by "--strict" checkpatch.
Ashutosh Dixit (1):
Intel MIC Driver Cleanups for "--strict" checkpatch.
Sudeep Dutt (3):
Intel MIC Host Driver Sysfs Cleanups.
Intel MIC Driver Header File Cleanups.
Intel MIC Header File warning fix.
Documentation/mic/mpssd/mpssd.c | 65 +++++++++++++------------
Documentation/mic/mpssd/sysfs.c | 4 +-
drivers/misc/mic/card/mic_debugfs.c | 2 +-
drivers/misc/mic/card/mic_device.c | 3 +-
drivers/misc/mic/card/mic_virtio.c | 19 ++++----
drivers/misc/mic/card/mic_x100.c | 6 +--
drivers/misc/mic/common/mic_dev.h | 51 +++++++++++++++++++
drivers/misc/mic/common/mic_device.h | 51 -------------------
drivers/misc/mic/host/mic_boot.c | 2 +-
drivers/misc/mic/host/mic_debugfs.c | 92 +++++++++++++++++------------------
drivers/misc/mic/host/mic_fops.c | 8 +--
drivers/misc/mic/host/mic_intr.c | 36 +++++++-------
drivers/misc/mic/host/mic_main.c | 2 +-
drivers/misc/mic/host/mic_smpt.c | 16 +++---
drivers/misc/mic/host/mic_sysfs.c | 94 +++++++++++++++---------------------
drivers/misc/mic/host/mic_virtio.c | 39 +++++++--------
drivers/misc/mic/host/mic_x100.c | 35 ++++++--------
include/uapi/linux/mic_ioctl.h | 2 +
18 files changed, 253 insertions(+), 274 deletions(-)
create mode 100644 drivers/misc/mic/common/mic_dev.h
delete mode 100644 drivers/misc/mic/common/mic_device.h
--
1.8.2.1
next reply other threads:[~2013-09-27 1:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 1:09 Sudeep Dutt [this message]
2013-09-27 1:09 ` [PATCH CHAR-MISC-NEXT 1/4] Intel MIC Host Driver Sysfs Cleanups Sudeep Dutt
2013-09-27 3:15 ` Greg Kroah-Hartman
2013-09-27 1:10 ` [PATCH CHAR-MISC-NEXT 2/4] Intel MIC Driver Header File Cleanups Sudeep Dutt
2013-09-27 3:16 ` Greg Kroah-Hartman
2013-09-27 1:10 ` [PATCH CHAR-MISC-NEXT 3/4] Intel MIC Driver Cleanups for "--strict" checkpatch Sudeep Dutt
2013-09-27 1:10 ` [PATCH CHAR-MISC-NEXT 4/4] Intel MIC Header File warning fix Sudeep Dutt
2013-09-27 3:17 ` Greg Kroah-Hartman
2013-09-27 19:37 ` Sudeep Dutt
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=cover.1380241770.git.sudeep.dutt@intel.com \
--to=sudeep.dutt@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=eddie.dong@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=harshavardhan.r.kharche@intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=peter.p.waskiewicz.jr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).