From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752934AbeA1Vrr (ORCPT ); Sun, 28 Jan 2018 16:47:47 -0500 Received: from mail.kernel.org ([198.145.29.99]:36012 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751816AbeA1Vro (ORCPT ); Sun, 28 Jan 2018 16:47:44 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2CF04217A0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Sun, 28 Jan 2018 15:47:41 -0600 From: Bjorn Helgaas To: Cyrille Pitchen Cc: bhelgaas@google.com, kishon@ti.com, lorenzo.pieralisi@arm.com, linux-pci@vger.kernel.org, adouglas@cadence.com, stelford@cadence.com, dgary@cadence.com, kgopi@cadence.com, eandrews@cadence.com, thomas.petazzoni@free-electrons.com, sureshp@cadence.com, nsekhar@ti.com, linux-kernel@vger.kernel.org, robh@kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v5 00/11] PCI: Add support to the Cadence PCIe controller Message-ID: <20180128214741.GA232763@bhelgaas-glaptop.roam.corp.google.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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