linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
	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: Sat, 11 Nov 2017 14:47:40 -0600	[thread overview]
Message-ID: <20171111204739.GC19895@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20171110104035.GA842@red-moon>

On Fri, Nov 10, 2017 at 10:40:35AM +0000, Lorenzo Pieralisi wrote:
> On Fri, Nov 10, 2017 at 08:46:29AM +0800, Shawn Lin wrote:
> > On 2017/11/9 23:05, Bjorn Helgaas wrote:

> > >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.

Yep, that's what I think, too.  My advice is to always use the
"master" branch of my tree as the base.  I use a lot of topic
branches, and they are almost always based on my "master".

There will be exceptions where that doesn't work because your patch
depends on something already in my tree or something in another tree.
But those are actually fairly rare, so just point that out in your
cover letter and we'll sort it out on a case-by-case basis.

Bjorn

  reply	other threads:[~2017-11-11 20:47 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 [this message]
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=20171111204739.GC19895@bhelgaas-glaptop.roam.corp.google.com \
    --to=helgaas@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --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 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).