From: Andy Lutomirski <luto@amacapital.net>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>,
Doug Thompson <dougthompson@xmission.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Borislav Petkov <bp@alien8.de>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 0/2] sb_edac: i2c_imc staging submission prep
Date: Thu, 14 Aug 2014 14:45:39 -0700 [thread overview]
Message-ID: <cover.1408051536.git.luto@amacapital.net> (raw)
I'd like to submit my i2c_imc driver to -staging, but the sb_edac
driver is currently squatting on my pci id :) sb_edac is a strange
beast: it uses registers from several PCI devcies, but the one that
it registers with the driver core is the SMBUS controller.
This trivial series moves sb_edac's PCI ids to pci_ids.h (they're
not exclusive to the EDAC hardware) and changes the PCI ID that is
used to detect the EDAC hardware.
I think that i2c_imc is a good staging candidate: the driver is IMO
quite clean, the hardware is very common, and I know of some users
(unrelated to me!) that use it for development, but it's not yet
acceptable as a real driver. In particular, it needs confirmation
from Intel as to whether it handshakes correctly with BIOS. In the
mean time, it's perfectly safe to use *if you know that your system
isn't doing something special with its DIMM SMBUS registers*.
I have reason to believe that I may be able to get a information
or a review from the right people at Intel in a couple of months,
and I suspect that some people in the NV-DIMM community would be
interested in this stuff.
I realize that the timing is a bit awkward here. These patches have
been floating around for almost a year. I'd be okay with them going
in for 3.17 or 3.18. If I understand correctly, the deadline for
staging drivers is much later than the merge window, but I don't
want to submit the i2c_imc driver itself to staging until these prep
patches are in.
Andy Lutomirski (2):
Move Intel SNB device ids from sb_edac to pci_ids.h
sb_edac: Claim a different PCI device
drivers/edac/sb_edac.c | 32 +-------------------------------
include/linux/pci_ids.h | 15 +++++++++++++++
2 files changed, 16 insertions(+), 31 deletions(-)
--
1.9.3
next reply other threads:[~2014-08-14 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 21:45 Andy Lutomirski [this message]
2014-08-14 21:45 ` [PATCH 1/2] Move Intel SNB device ids from sb_edac to pci_ids.h Andy Lutomirski
2014-09-05 23:41 ` Bjorn Helgaas
2014-09-05 23:42 ` Andy Lutomirski
2014-09-08 14:08 ` Aristeu Rozanski
2014-08-14 21:45 ` [PATCH 2/2] sb_edac: Claim a different PCI device Andy Lutomirski
2014-09-08 14:10 ` Aristeu Rozanski
2014-09-08 21:49 ` Andy Lutomirski
2014-09-08 23:41 ` Greg Kroah-Hartman
2014-09-09 9:25 ` Mauro Carvalho Chehab
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.1408051536.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=m.chehab@samsung.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).