From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751627AbcBHLeq (ORCPT ); Mon, 8 Feb 2016 06:34:46 -0500 Received: from us01smtprelay-2.synopsys.com ([198.182.47.9]:51480 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751102AbcBHLeo (ORCPT ); Mon, 8 Feb 2016 06:34:44 -0500 Subject: Re: [PATCH v3] synopsys pcie rc generic platform driver update To: Bjorn Helgaas , Joao Pinto References: <28b04a32cc7caf6db542d4b5aa1feddacd02b2c9.1454701564.git.jpinto@synopsys.com> <20160205225204.GB11780@localhost> CC: , , , , From: Joao Pinto Message-ID: <56B87D4F.2080009@synopsys.com> Date: Mon, 8 Feb 2016 11:34:39 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160205225204.GB11780@localhost> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.13.184.19] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bjorn, I am going to produce a patch just for the centralization of driver common code first. Then we need to discuss a bit what to do in order to transform pcie-designware into an hybrid driver (function lib and platform driver). BR Joao On 2/5/2016 10:52 PM, Bjorn Helgaas wrote: > Hi Joao, > > On Fri, Feb 05, 2016 at 07:55:43PM +0000, Joao Pinto wrote: >> This patch tries to improve the host/pcie-synopsys branch including a new >> driver name, more accurate documentation and centralized link up validation. >> Other platform drivers were also updated to include the new centralized link >> up validation function. > > It's true that I wanted you to incorporate a few tweaks I had made in > my pci/host-synopsys branch, but generating incremental patches on top > of that branch makes this too confusing to follow. > > My pci/host-synopsys contains two patches on top of v4.5-rc1. I would > prefer that you > > - fetch that branch, > - make whatever edits you need, and > - generate fresh patches based on v4.5-rc1 > > Then everybody can see the whole series at once without trying to > integrate these changes with the ones you've previously posted, and I > can start from scratch and apply those fresh patches on top of > v4.5-rc1. > > It's good that you include summaries of what's changed between > versions, but if people want to see *exactly* what's changed between > your v3 and v4 postings, it's easy for them to download those series, > apply them on different branches, and git diff the branches. > > Bjorn >