From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-pci@vger.kernel.org,
Jiang Liu <jiang.liu@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dan Williams <dan.j.williams@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Bryan Veal <bryan.e.veal@intel.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Martin Mares <mj@ucw.cz>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCHv7 0/6] Driver for new "VMD" device
Date: Mon, 11 Jan 2016 15:15:29 -0600 [thread overview]
Message-ID: <20160111211529.GA13475@localhost> (raw)
In-Reply-To: <20160111204911.GB8743@localhost.localdomain>
On Mon, Jan 11, 2016 at 08:49:11PM +0000, Keith Busch wrote:
> > x86-pci-initial-commit-for-new
> > -:125: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
>
> Question on the maintenance: does this new driver file need a maintainer,
> or does it fall under arch/x86/pci/ umbrella? I'm happy to supply updates
> and/or fixes once this is merged, but I just want to understand who to
> direct patches/pull requests to if the need arises.
It might be worth adding a MAINTAINERS update, similar to the
"PCI DRIVER" entries we have for host bridge drivers. In those
cases, I take care of merging updates and sending them to Linus,
but I do ask for an ack from the listed maintainer for non-trivial
changes.
Bjorn
prev parent reply other threads:[~2016-01-11 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 17:44 [PATCHv7 0/6] Driver for new "VMD" device Keith Busch
2015-12-21 17:44 ` [PATCHv7 1/6] msi: Relax msi_domain_alloc() to support parentless MSI irqdomains Keith Busch
2015-12-21 17:44 ` [PATCHv7 2/6] PCI/MSI: Export msi functions for module use Keith Busch
2015-12-21 17:44 ` [PATCHv7 3/6] x86/IRQ: Export IRQ domain function " Keith Busch
2015-12-21 17:44 ` [PATCHv7 4/6] x86/PCI: Allow PCI domain specific dma ops Keith Busch
2015-12-21 17:44 ` [PATCHv7 5/6] x86/PCI: Initial commit for new VMD device driver Keith Busch
2015-12-21 17:45 ` [PATCHv7 6/6] PCI/AER: Use 32 bit int type domains Keith Busch
2016-01-06 20:03 ` [PATCHv7 0/6] Driver for new "VMD" device Keith Busch
2016-01-08 9:47 ` Thomas Gleixner
2016-01-11 17:06 ` Bjorn Helgaas
2016-01-11 20:49 ` Keith Busch
2016-01-11 21:15 ` Bjorn Helgaas [this message]
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=20160111211529.GA13475@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bryan.e.veal@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mj@ucw.cz \
--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).