linux-kernel - Re: [PATCH v5 0/4] Add Broadcom North Star 2 support

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:	Tue, 28 Jul 2015 12:55:56 +0200
From:	Olof Johansson <olof@...om.net>
To:	Ray Jui <rjui@...adcom.com>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Arnd Bergmann <arnd@...db.de>,
	Mark Rutland <mark.rutland@....com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Hauke Mehrtens <hauke@...ke-m.de>,
	linux-kernel@...r.kernel.org,
	bcm-kernel-feedback-list@...adcom.com,
	linux-arm-kernel@...ts.infradead.org, arm@...nel.org,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH v5 0/4] Add Broadcom North Star 2 support

On Mon, Jul 27, 2015 at 03:42:17PM -0700, Ray Jui wrote:
> This patch series adds Broadcom North Star 2 (NS2) SoC support. NS2 is an ARMv8
> based SoC and under the Broadcom iProc family.
> 
> Sorry for tying this with the Broadcom iProc PCIe driver fixes for ARM64. I
> have to tie them together because iProc PCIe support is enabled by default
> when ARCH_BCM_IPROC is enabled. Without the fixes in the iProc PCIe driver,
> enabling CONFIG_ARCH_BCM_IPROC would break the build for arm64 defconfig. Let
> me know if there's a better way to handle this.

One common way to handle it is that instead of sitting on the patch to fix PCI
for months, you post that early such that when the rest is posted, it's been in
the kernel for a long time.

In practice, that's sometimes hard to do, but it's the ideal situation.

Anyway, I've queued up these patches for 4.3. Thanks!


-Olof

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