linux-kernel - Re: PCI host merge strategy and maintainers

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 26 Sep 2013 10:32:32 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
CC:	Frank Li <lznuaa@...il.com>, Jason Cooper <jason@...edaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Jingoo Han <jg1.han@...sung.com>,
	Thierry Reding <thierry.reding@...il.com>,
	Andrew Lunn <andrew@...n.ch>,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	Kevin Hilman <khilman@...aro.org>,
	Stephen Warren <swarren@...dia.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: PCI host merge strategy and maintainers

Hi Bjorn,

On Wed, Sep 25, 2013 at 05:28:28PM -0600, Bjorn Helgaas wrote:
> There are patches for exynos, imx6, mvebu, and tegra on the PCI list,
> and I want to sort out how people expect them to be merged.
> 
> My current assumption is the following:
> 
>   drivers/pci/host/pcie-designware.c  via PCI tree since I applied
> recent changes
>   drivers/pci/host/pci-exynos.c  via PCI tree since I applied recent changes
>   drivers/pci/host/pci-imx6.c  via Shawn Guo per [1]

A second thought on that.  I would split the patch for better separation
between driver and arch parts, so that they can go through PCI and
arm-soc tree separately without worrying about merge conflict later.

I will send you patches that we expect to go via your tree in a few
minutes.

Shawn

>   drivers/pci/host/pci-mvebu.c  ?? unclear; Jason Cooper has merged
> some, I've merged some
>   drivers/pci/host/pci-tegra.c  via PCI tree per Stephen Warren [2]
> 
> Please correct anything that's wrong above, and please give me some
> guidance on mvebu.  I'm happy to go either way; I just need to know
> whether to pay attention to them :)
> 
> In addition, since I don't have time, expertise, or hardware to really
> review changes to these drivers, I'd like to have them acked by people
> who do.  My current assumption is that these are the right people:
> 
>   designware: Jingoo Han <jg1.han@...sung.com>
>   exynos: Jingoo Han <jg1.han@...sung.com>
>   imx6: Shawn Guo <shawn.guo@...aro.org>
>   mvebu: Jason Cooper <jason@...edaemon.net>, Andrew Lunn
> <andrew@...n.ch>, Gregory Clement <gregory.clement@...e-electrons.com>
>   tegra: Thierry Reding <thierry.reding@...il.com>
> 
> Again, please correct anything that's wrong.  My plan is that I won't
> apply patches to these drivers unless they're acked by the folks
> above.
> 
> Bjorn
> 
> 
> [1] http://lkml.kernel.org/r/20130916091059.GM31147@S2101-09.ap.freescale.net
> [2] http://lkml.kernel.org/r/521CCF9B.9000004@wwwdotorg.org

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/