All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add Lorenzo Pieralisi for PCI host bridge drivers
Date: Fri, 10 Nov 2017 10:40:35 +0000	[thread overview]
Message-ID: <20171110104035.GA842@red-moon> (raw)
In-Reply-To: <c990c9af-7d7c-27f9-30e5-2ebda49b8b3b@rock-chips.com>

On Fri, Nov 10, 2017 at 08:46:29AM +0800, Shawn Lin wrote:
> Hi Bjorn,
> 
> On 2017/11/9 23:05, 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).
> >
> >
> >commit 6b7be529634bbfbf6395f23217a66d731fbed0a0
> >Author: Bjorn Helgaas <bhelgaas@google.com>
> >Date:   Wed Nov 8 08:49:49 2017 -0600
> >
> >     MAINTAINERS: Add Lorenzo Pieralisi for PCI host bridge drivers
> >     Add Lorenzo Pieralisi as maintainer for PCI native host bridge drivers and
> >     the endpoint driver framework.
> >     Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> >     Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> >
> >diff --git a/MAINTAINERS b/MAINTAINERS
> >index db412a627d96..6ce341e86fec 100644
> >--- a/MAINTAINERS
> >+++ b/MAINTAINERS
> >@@ -10378,6 +10378,7 @@ F:	drivers/pci/dwc/*keystone*
> >  PCI ENDPOINT SUBSYSTEM
> >  M:	Kishon Vijay Abraham I <kishon@ti.com>
> >+M:	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> >  L:	linux-pci@vger.kernel.org
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kishon/pci-endpoint.git
> >  S:	Supported
> >@@ -10429,6 +10430,15 @@ F:	include/linux/pci*
> >  F:	arch/x86/pci/
> >  F:	arch/x86/kernel/quirks.c
> >+PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS
> >+M:	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> >+L:	linux-pci@vger.kernel.org
> >+Q:	http://patchwork.ozlabs.org/project/linux-pci/list/
> >+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/
> 
> So, does that mean the patch(es) for host drivers shoube be based on
> this tree instead of yours? If yes, which tree should be preferred if
> a patchset wanna touch both of pci core and host drivers?

I think you should always use Bjorn's tree as a reference and we
will sort out the dependencies.

Thanks,
Lorenzo

  reply	other threads:[~2017-11-10 10:40 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 [this message]
2017-11-11 20:47           ` Bjorn Helgaas
2017-11-10  5:46       ` Kishon Vijay Abraham I
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=20171110104035.GA842@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=helgaas@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=shawn.lin@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.