linux-kernel - Re: [PATCH v5 00/11] PCI: Add support to the Cadence PCIe controller

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:   Sun, 28 Jan 2018 15:47:41 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Cyrille Pitchen <cyrille.pitchen@...e-electrons.com>
Cc:     bhelgaas@...gle.com, kishon@...com, lorenzo.pieralisi@....com,
        linux-pci@...r.kernel.org, adouglas@...ence.com,
        stelford@...ence.com, dgary@...ence.com, kgopi@...ence.com,
        eandrews@...ence.com, thomas.petazzoni@...e-electrons.com,
        sureshp@...ence.com, nsekhar@...com, linux-kernel@...r.kernel.org,
        robh@...nel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v5 00/11] PCI: Add support to the Cadence PCIe controller

On Sun, Jan 28, 2018 at 09:40:14PM +0100, Cyrille Pitchen wrote:
> Hi all,
> 
> this series of patches adds support to the Cadence PCIe controller.
> It was tested on a ARM64 platform emulated by a Palladium running the
> pci-next kernel.
> 
> The host mode was tested with some PCIe devices connected to the Palladium
> through a speed-bridge. Some of those devices were a USB host controller
> and a SATA controller. The PCIe host controller was also tested with a
> second controller configured in endpoint mode and connected back to back
> to the first controller.
> 
> The EndPoint Controller (EPC) driver was tested with 2 PCI functions, both
> handled by the pci-epf-test driver, using the pcitest userspace program.
> I used the "-D" optional command line parameter to select the proper PCI
> function.
> 
> Best regards,
> 
> Cyrille
> 
> ChangeLog
> 
> v4 -> v5:
> - rebase on today's (20180128) linux-pci/next

Don't bother rebasing onto linux-pci/next.

If your patches actually *depend* on something that has already been
merged onto a PCI topic branch, you should mention that and say which
branch.

But otherwise, it's easiest if they are based on linux-pci/master,
because that's how Lorenzo and I apply them.

linux-pci/next is ephemeral and I frequently rebuild it to fix errors,
add acks, etc.

It doesn't *hurt* that you rebased, but it doesn't help anything
either, and it's a little needless work for you.

Bjorn