From: Kishon Vijay Abraham I <kishon@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add Lorenzo Pieralisi for PCI host bridge drivers
Date: Fri, 10 Nov 2017 11:16:24 +0530 [thread overview]
Message-ID: <e1c5d6fe-3709-1931-dbac-010ac7751ba2@ti.com> (raw)
In-Reply-To: <20171109150528.GA7629@bhelgaas-glaptop.roam.corp.google.com>
Hi,
On Thursday 09 November 2017 08:35 PM, Bjorn Helgaas wrote:
> On Thu, Nov 09, 2017 at 11:28:36AM +0530, Kishon Vijay Abraham I wrote:
>> Hi Bjorn,
>>
>> On Thursday 09 November 2017 01:56 AM, Bjorn Helgaas wrote:
>>> On Wed, Nov 08, 2017 at 02:15:10PM -0600, Bjorn Helgaas wrote:
>>>> From: Bjorn Helgaas <bhelgaas@google.com>
>>>>
>>>> Add Lorenzo Pieralisi as maintainer for PCI native host bridge drivers and
>>>> the endpoint driver framework.
>>>>
>>>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>>>
>>> This is on my for-linus branch, and I intend to merge it for v4.14.
>>
>> There is already an entry for PCI endpoint in MAINTAINERS file. Can Lorenzo be
>> added there?
>>
>> PCI ENDPOINT SUBSYSTEM
>> M: Kishon Vijay Abraham I <kishon@ti.com>
>> L: linux-pci@vger.kernel.org
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/kishon/pci-endpoint.git
>> S: Supported
>> F: drivers/pci/endpoint/
>> F: drivers/misc/pci_endpoint_test.c
>> F: tools/pci/
>
> Right, thanks, I forgot all about this separate entry. I added Lorenzo
> there, resulting in the patch below.
>
> My practice has been that all the PCI patches (everything in
> drivers/pci plus some include and x86/pci stuff) have been merged via
> my tree.
>
> This includes things in drivers/pci/{host,dwc,endpoint,switch}, which
> are non-core things and usually specific to a chipset. I try to
> ensure they have individual maintainers designated, and I ask for
> their acks for non-trivial changes because I have no specs and no
> hardware for testing them. But I think it's still good to have one
> person look over them all to try to keep some consistency across them
> because they are all quite similar.
>
> So my hope is that Lorenzo can take over that oversight role from me,
> not that he would replace any of those designated maintainers.
>
> Ideally, this will be transparent to patch submitters except that they
> should add Lorenzo to the "To:" line (keeping linux-pci and other
> interested parties).
Makes sense.
I'm also thinking if we should change the tree in PCI ENDPOINT SUBSYSTEM to
git git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git or maybe
git git://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/?
since most of the endpoint patches also deals with modifying the controller
drivers.
Thanks
Kishon
next prev parent reply other threads:[~2017-11-10 5:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:15 [PATCH] MAINTAINERS: Add Lorenzo Pieralisi for PCI host bridge drivers Bjorn Helgaas
2017-11-08 20:26 ` Bjorn Helgaas
2017-11-09 5:58 ` Kishon Vijay Abraham I
2017-11-09 10:12 ` Lorenzo Pieralisi
2017-11-09 15:05 ` Bjorn Helgaas
2017-11-10 0:46 ` Shawn Lin
2017-11-10 10:40 ` Lorenzo Pieralisi
2017-11-11 20:47 ` Bjorn Helgaas
2017-11-10 5:46 ` Kishon Vijay Abraham I [this message]
2017-11-09 10:47 ` Lorenzo Pieralisi
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=e1c5d6fe-3709-1931-dbac-010ac7751ba2@ti.com \
--to=kishon@ti.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).