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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A1AC7ECAAD4 for ; Tue, 30 Aug 2022 09:32:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231934AbiH3Jcs (ORCPT ); Tue, 30 Aug 2022 05:32:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231887AbiH3Jc1 (ORCPT ); Tue, 30 Aug 2022 05:32:27 -0400 Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA8CFDEA7C for ; Tue, 30 Aug 2022 02:32:08 -0700 (PDT) Received: by mail-lf1-x12a.google.com with SMTP id w8so5648133lft.12 for ; Tue, 30 Aug 2022 02:32:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=DI8R5uBfUCPdaITMxiTJ7CTu8pb9+geNomuQXiCpnr0=; b=EI+kX0MIh7dM75jIWk5kzV+psrJX2vqVdAV3nYBd368tgD9H4/7BQNqg/NqSfxwQWw NO52QwNk1KHMnuXWgM0aY13g4hlfug1T2ig/krnVYsA0T66MxhlBMCvkhCqUvOw0ywqG bDzuxncaHbd25Zpu1lkX5ZY4cnBXfS++ss7GhLx+Op2yAf+vBD2s+ol8DTusmln4r+mu NrxlZ0tW6emLdtJPTFReevrJghIz6LpvusVer4pP5dZAaQMXsRtDPa7KmmUjle9Dp0l+ MpNw5gCu8Qp2Ygqg1i+tGXvAizICUojIuJyW0lNihDW/8Yv7cNv0W5UqnwtWTZDkuaSl BCPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=DI8R5uBfUCPdaITMxiTJ7CTu8pb9+geNomuQXiCpnr0=; b=mPCuiE67Q7k47GlT/ZmIwhwaru/RZRfAW0qtYz++hYZnHWsAHoNHmPwYRugXMkQuPY btZ+MCsau7Alh9f0/InYSMWFda5feBQNl/FF4PhI50PWd1ZdRUDYlqJ8VUfU6byVSmBl R9/n3s+Q6wvUpbDgGINYm/vszF2FMMHvGxxQuafJIwqQdr1FdmpcVr6JJrYRmv5EBOIm g5LvE4aKa2DwjaK+Drp624DlZkCD/8rm2Qgi6bJJ3CX2ZzJiFY1KrK0SHOBUFg4szMLq 6lK6dVnAY+AYZlOQvJhNkp+3acItBdkbdq07iZbbWpXVv0O3ZXjeni2PhkK1wjCK7NzM nbqg== X-Gm-Message-State: ACgBeo3s+0LoPDWclHBw3b3yWFHKWemiI8TUWk/nLDmm9Cebpk/gS19Q iGPp9Ba9MAzDU6wNSexsmD5IUA== X-Google-Smtp-Source: AA6agR5pvdm6ppGDodlxvczV0eI5jT2RR3G29/7S9uRukhMpYXw8vrXirlsmxe2a8LQqnM76clooew== X-Received: by 2002:a05:6512:261b:b0:492:cd8a:e1c with SMTP id bt27-20020a056512261b00b00492cd8a0e1cmr7173154lfb.528.1661851925857; Tue, 30 Aug 2022 02:32:05 -0700 (PDT) Received: from [192.168.1.211] ([37.153.55.125]) by smtp.gmail.com with ESMTPSA id a28-20020a2eb55c000000b0025e2c5a12b6sm828961ljn.129.2022.08.30.02.32.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 Aug 2022 02:32:05 -0700 (PDT) Message-ID: Date: Tue, 30 Aug 2022 12:32:04 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.1.2 Subject: Re: [PATCH v3 00/30] phy: qcom,qmp: fix dt-bindings and deprecate lane suffix Content-Language: en-GB To: Johan Hovold , Vinod Koul Cc: Johan Hovold , Rob Herring , Krzysztof Kozlowski , Andy Gross , Bjorn Andersson , Konrad Dybcio , Kishon Vijay Abraham I , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220714124333.27643-1-johan+linaro@kernel.org> From: Dmitry Baryshkov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30/08/2022 10:01, Johan Hovold wrote: > On Tue, Aug 30, 2022 at 10:36:43AM +0530, Vinod Koul wrote: >> On 14-07-22, 14:43, Johan Hovold wrote: [skipped] >>> The final patches add support for the updated binding to the (recently >>> split up) PHY drivers. Included is also a related combo PHY cleanup. >> >> This fails at patch 2 for me on v6.0-rc1, please rebase and resend > > Are you sure you haven't applied anything to your local tree that causes > this? When doing the QMP split, we ended up in a similar situation if I remember correctly. Most probably the easiest way is to provide a branch for Vinod to pull in addition to the patches being sent to ML. > I just tried fetching the v3 series from lore and it applies just fine > on top of 6.0-rc1. > > Note that if you've added a new compatible string locally, the second > patch which sorts the compatible strings is likely to fail to apply. > > Johan -- With best wishes Dmitry