linux-kernel - Re: [PATCH] MAINTAINERS: Add Lorenzo Pieralisi for PCI host bridge drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 11 Nov 2017 14:47:40 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc:     Shawn Lin <shawn.lin@...k-chips.com>,
        Kishon Vijay Abraham I <kishon@...com>,
        linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add Lorenzo Pieralisi for PCI host bridge
 drivers

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@...com>
> > >+M:	Lorenzo Pieralisi <lorenzo.pieralisi@....com>
> > >  L:	linux-pci@...r.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@....com>
> > >+L:	linux-pci@...r.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