From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3D7A0C04FF6 for ; Fri, 12 Apr 2024 12:43:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=65C0Xo1faPcfpbZ18CGc8OPZa/GQ2QM08WI2Z03o1kg=; b=yMqoCfX6EXDn1k u/js+hUIuxTM5pHY4DZhMGJiCXbieW4PMQLOccrViwdRvAm9QfN/5yLC3APL4byMc5MiNCi6ylReu Zx8BPlf8HtNuSQv2tvxYnRzsmwHnzq7wzWqZqb4DOjEVgiH4BCzYXdraU+s6EVoRcFUBBPsQ+tiiA 6ESnXCOYJrzesW+Jl5XuU+J2+zxxzbajjpV2WzV9vy8FiaPyqbWrvR7znnYkZWcW4P7MCuXMGVW0k BDi0Zrbg00gQZpi2CI0rRXHoHBgFfUP3J+0AVyC5NH0LA25c+dmQ76UyQUYKlmymfC/+OHqOmXTOe UchFiqc14TinWKbyOk4g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rvGF3-0000000H9ou-017L; Fri, 12 Apr 2024 12:42:53 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rvGF0-0000000H9o4-0ZYm; Fri, 12 Apr 2024 12:42:51 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id E057ACE38AB; Fri, 12 Apr 2024 12:42:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 19F31C113CC; Fri, 12 Apr 2024 12:42:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1712925767; bh=RFZZ+mGFrMvvzGP+Wwx3ZJjWKuRdZUpn09zEfdGc7P0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=f4nYe/em6FK0f+oAwuh0E1rMXQ1OyU4HGcc0d3wGEkQs8c01qL+qYZXK7o533Ysy4 12FEaeYNYxLWiGTQZbgfQMmJRnPAIosXSS6Zww3JQkROF0SrSm9b1ggXg6zLAYYwKO odOnXedPol5+Z1ADVvnwDXI7aPmAXVzsYC7lgNGgKqiSH+rgcBS7HfOj6+CsmkRYZw DRCJo2Rlk4oN1rmCBnunXTTJfaA9Nl+2iXXwuyCohy8+z6igI07gVChSGzHOp3wIZa JaY092JRKQkFik2TB+OLe0WFl/4PQtSCz8HtXg7oFHfb6dT/JeAcwQkYR72H3Olyk3 ns6WGTbpiZsiA== Date: Fri, 12 Apr 2024 14:42:41 +0200 From: Niklas Cassel To: Vinod Koul Cc: Kishon Vijay Abraham I , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner , devicetree@vger.kernel.org, Sebastian Reichel , Michal Tomek , Damien Le Moal , Jon Lin , linux-phy@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org Subject: Re: [PATCH 0/2] rockchip pcie3-phy separate refclk support Message-ID: References: <20240411130150.128107-1-cassel@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240412_054250_380450_47895976 X-CRM114-Status: GOOD ( 14.98 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Apr 12, 2024 at 03:03:59PM +0530, Vinod Koul wrote: > Hi Niklas, > > On 11-04-24, 15:01, Niklas Cassel wrote: > > This series is based on: linux-phy phy/fixes > > (Since there are other rockchip,pcie3-phy changes there that have not > > yet reached mainline and which would otherwise have caused conflicts.) > > I merged the fixes into next and tried to apply this patch but second > one fails for me. I guess it needs to be rebased. > > Always based these changes on phy/next or phy/fixes+next (which is what > I will end up with to resolve) I based it on phy/fixes since there were commits for this driver in phy/fixes that were not in phy/next, so I did it for you to not get conflicts :) Since this still gave you conflicts, there must have been other changes in phy/next for this driver. I must have missed that, sorry. I see that you have now merged phy/fixes into phy/next, that will make things easier, thank you. I will send out a V2 based on phy/next shortly. Kind regards, Niklas _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel