[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160111204911.GB8743@localhost.localdomain>
Date: Mon, 11 Jan 2016 20:49:11 +0000
From: Keith Busch <keith.busch@...el.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
linux-pci@...r.kernel.org, Jiang Liu <jiang.liu@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Dan Williams <dan.j.williams@...el.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Bryan Veal <bryan.e.veal@...el.com>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Martin Mares <mj@....cz>,
Jon Derrick <jonathan.derrick@...el.com>
Subject: Re: [PATCHv7 0/6] Driver for new "VMD" device
Hi Bjorn,
Thanks for the catches. Most were simple fixes, and I used your
cleanup suggestions for others. Will resend shortly.
On Mon, Jan 11, 2016 at 11:06:17AM -0600, Bjorn Helgaas wrote:
> Checkpatch complained about a few things that should be easy to fix up:
>
> x86-pci-allow-pci-domain
> -:26: WARNING: struct dma_map_ops should normally be const
> 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.
Powered by blists - more mailing lists