From: Keith Busch <keith.busch@intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-pci@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Bryan Veal <bryan.e.veal@intel.com>,
Jon Derrick <jonathan.derrick@intel.com>,
Keith Busch <keith.busch@intel.com>
Subject: [PATCHv8] Driver for new "VMD" device
Date: Tue, 12 Jan 2016 09:28:38 -0700 [thread overview]
Message-ID: <1452616119-11450-1-git-send-email-keith.busch@intel.com> (raw)
This is just the commit for the VMD driver. The other patches are the
same from previous series here:
https://lkml.org/lkml/2015/12/21/353
Patch 2/6 is no longer applicable since someone already beat me to
exporting those functions to API in commit a4289dc2ec3a5. Otherwise the
others are still needed and cleanly apply. I wasn't sure if I should
repost the entire series or just the one file that changed.
Changes since v7 are all checkpatch fixes:
Fixing 80 character lines.
Spacing, tabbing and new line fixes.
A macro semicolon fix.
An entry in the MAINTAINERS file.
The only checkpatch issue reported is warning on a normally "const"
struct, but the warning is not applicable for the usage.
Keith Busch (1):
x86/PCI: Initial commit for new VMD device driver
MAINTAINERS | 6 +
arch/x86/Kconfig | 13 +
arch/x86/include/asm/hw_irq.h | 5 +
arch/x86/pci/Makefile | 2 +
arch/x86/pci/vmd.c | 699 ++++++++++++++++++++++++++++++++++++++++++
5 files changed, 725 insertions(+)
create mode 100644 arch/x86/pci/vmd.c
--
2.6.2.307.g37023ba
next reply other threads:[~2016-01-12 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 16:28 Keith Busch [this message]
2016-01-12 16:28 ` [PATCHv8] x86/PCI: Initial commit for new VMD device driver Keith Busch
2016-01-12 17:40 ` kbuild test robot
2016-01-12 18:08 ` Keith Busch
2016-01-12 19:42 ` Bjorn Helgaas
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=1452616119-11450-1-git-send-email-keith.busch@intel.com \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=bryan.e.veal@intel.com \
--cc=dan.j.williams@intel.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).