Received: by 2002:a05:7412:d8a:b0:e2:908c:2ebd with SMTP id b10csp2691610rdg; Mon, 16 Oct 2023 11:44:20 -0700 (PDT) X-Google-Smtp-Source: AGHT+IETzPLvlWmnG3MerW0jhNfH/R5b+a5/0+jGF5k6zHTunQChMdJSt/OpHAzjm5MWDeGjSGed X-Received: by 2002:a05:6a00:24cd:b0:690:cae9:714d with SMTP id d13-20020a056a0024cd00b00690cae9714dmr21011pfv.13.1697481859909; Mon, 16 Oct 2023 11:44:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697481859; cv=none; d=google.com; s=arc-20160816; b=S27C6vDJvz3FjFfYoLKc10u039qU2zV04O72jbJnpzD4A8srliIptDykdIPtjay6Ct qkZByZtNO3exki8rKc4KxiM8o+5Z5pSm6iEEBKZXlcM6Xaqqzdv67/u8cOD+jfDYNCio 4DjfjcodEHaeGaRsNWHWQxIK2c23hOzhfJCslriCmH2rnoZI9wMmHp5dxwebk3ASwvmn RO9RkOQCBmwwO6q/DBUxudQxBNGor+J1AWZ3Slm9lhnmb3ESZAFLPWS+qjQue0oMiR3J tl/Cml2UKUieZxabInhz5mEGdSVrhAfaZSXJhIlUWoups8DNqXeXNVR6viaUOtzUaWrZ VPNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=x3znpD/RtyFNwdfpvnDyZQmBNYjIwwqNzW9eD3TYxgI=; fh=ekKS79oux6nDmKfwiHARrNcQ9pEmhb+x7W779hGzIr4=; b=xEhHElCidUWyTGyyZVGE+XWkbZ2XbkzQbnR1nUeeoAIclf6g/i7qbOBJ6d8v0fAQzI 9fXXI2//gd38c6Kk+TqLYordWtFC0AuJ/fo4eubngksmG0BY2ru4ceL9wBj3KJdIucgA fFEEok5VRwvwQSUBbs3hJ54P6L1Ub7qUGsp4OKzgauX0WWKAcTyXnjnShuv4juZOtxVC LhXQzUDlKex6qlcr9rDte9xEl6G57A4SOzTlmXN3B/JZJ96TScfqgLBuP7r495KTFcj0 oazCty9dehOBoQTVQ2/wN79uN1OegasR99FYgWSJfPTdN3o7A39dTE9y7BBUnaLThkuZ E+9g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=oAbWha35; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from howler.vger.email (howler.vger.email. [2620:137:e000::3:4]) by mx.google.com with ESMTPS id q19-20020a056a00151300b006ba8478b96fsi393297pfu.30.2023.10.16.11.44.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Oct 2023 11:44:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=oAbWha35; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id 324BF804911F; Mon, 16 Oct 2023 11:44:16 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233767AbjJPSoA (ORCPT + 99 others); Mon, 16 Oct 2023 14:44:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45684 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229459AbjJPSn7 (ORCPT ); Mon, 16 Oct 2023 14:43:59 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A667995; Mon, 16 Oct 2023 11:43:57 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BEBAEC433C8; Mon, 16 Oct 2023 18:43:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1697481837; bh=EXdxbvlR0cbgdx4LvLwELq1zkDK3jwhg8mze2b9ktT8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oAbWha35MgjQMlGt0UAk14DYTqoC6rn8fpoaNl0AAocdRaMdn5w34NsUJV93EgpTG RSFw5i4Lt5Lp4xrS2MBztDeBRT4UUcu1NDJoTjG7XLVhKIarhZGXpK9vfoLPZEoUIs ztF4yM1cgX7Oh5izJ+5QLCttqhOop+74txm6D+JA= Date: Mon, 16 Oct 2023 20:43:54 +0200 From: Greg KH To: Rohit Agarwal Cc: Dmitry Baryshkov , vkoul@kernel.org, Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the usb tree Message-ID: <2023101619-dumpster-vigorous-f9b4@gregkh> References: <20231004132247.01c3bfeb@canb.auug.org.au> <2023100410-concave-explore-95bf@gregkh> <2023100445-cymbal-glade-52c8@gregkh> <044a2146-f859-44b3-bcf7-66b68d3e7787@quicinc.com> <2023100912-tiara-pout-ba98@gregkh> <502135a8-6e82-4361-b0fc-e683694ca2cd@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <502135a8-6e82-4361-b0fc-e683694ca2cd@quicinc.com> X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on howler.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Mon, 16 Oct 2023 11:44:16 -0700 (PDT) On Thu, Oct 12, 2023 at 10:33:28PM +0530, Rohit Agarwal wrote: > > On 10/9/2023 3:19 PM, Dmitry Baryshkov wrote: > > On Mon, 9 Oct 2023 at 12:48, Greg KH wrote: > > > On Mon, Oct 09, 2023 at 02:48:27PM +0530, Rohit Agarwal wrote: > > > > On 10/4/2023 6:16 PM, Greg KH wrote: > > > > > On Wed, Oct 04, 2023 at 12:17:27PM +0530, Rohit Agarwal wrote: > > > > > > On 10/4/2023 12:13 PM, Greg KH wrote: > > > > > > > On Wed, Oct 04, 2023 at 01:22:47PM +1100, Stephen Rothwell wrote: > > > > > > > > Hi all, > > > > > > > > > > > > > > > > After merging the usb tree, today's linux-next build (x86_64 allmodconfig) > > > > > > > > failed like this: > > > > > > > > > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:156:43: error: 'QPHY_V6_PCS_SW_RESET' undeclared here (not in a function); did you mean 'QPHY_V2_PCS_SW_RESET'? > > > > > > > > 156 | [QPHY_SW_RESET] = QPHY_V6_PCS_SW_RESET, > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~ > > > > > > > > | QPHY_V2_PCS_SW_RESET > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:157:43: error: 'QPHY_V6_PCS_START_CONTROL' undeclared here (not in a function); did you mean 'QPHY_V3_PCS_START_CONTROL'? > > > > > > > > 157 | [QPHY_START_CTRL] = QPHY_V6_PCS_START_CONTROL, > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > | QPHY_V3_PCS_START_CONTROL > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:158:43: error: 'QPHY_V6_PCS_PCS_STATUS1' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_PCS_STATUS1'? > > > > > > > > 158 | [QPHY_PCS_STATUS] = QPHY_V6_PCS_PCS_STATUS1, > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > | QPHY_V5_PCS_PCS_STATUS1 > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:159:43: error: 'QPHY_V6_PCS_POWER_DOWN_CONTROL' undeclared here (not in a function); did you mean 'QPHY_V3_PCS_POWER_DOWN_CONTROL'? > > > > > > > > 159 | [QPHY_PCS_POWER_DOWN_CONTROL] = QPHY_V6_PCS_POWER_DOWN_CONTROL, > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > | QPHY_V3_PCS_POWER_DOWN_CONTROL > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:162:43: error: 'QPHY_V6_PCS_USB3_AUTONOMOUS_MODE_CTRL' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_USB3_AUTONOMOUS_MODE_CTRL'? > > > > > > > > 162 | [QPHY_PCS_AUTONOMOUS_MODE_CTRL] = QPHY_V6_PCS_USB3_AUTONOMOUS_MODE_CTRL, > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > | QPHY_V5_PCS_USB3_AUTONOMOUS_MODE_CTRL > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:163:44: error: 'QPHY_V6_PCS_USB3_LFPS_RXTERM_IRQ_CLEAR' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_USB3_LFPS_RXTERM_IRQ_CLEAR'? > > > > > > > > 163 | [QPHY_PCS_LFPS_RXTERM_IRQ_CLEAR] = QPHY_V6_PCS_USB3_LFPS_RXTERM_IRQ_CLEAR, > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > | QPHY_V5_PCS_USB3_LFPS_RXTERM_IRQ_CLEAR > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:991:26: error: 'QPHY_V6_PCS_LOCK_DETECT_CONFIG1' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_LOCK_DETECT_CONFIG1'? > > > > > > > > 991 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_LOCK_DETECT_CONFIG1, 0xc4), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:992:26: error: 'QPHY_V6_PCS_LOCK_DETECT_CONFIG2' undeclared here (not in a function); did you mean 'QPHY_V3_PCS_LOCK_DETECT_CONFIG2'? > > > > > > > > 992 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_LOCK_DETECT_CONFIG2, 0x89), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:993:26: error: 'QPHY_V6_PCS_LOCK_DETECT_CONFIG3' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_LOCK_DETECT_CONFIG3'? > > > > > > > > 993 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_LOCK_DETECT_CONFIG3, 0x20), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:994:26: error: 'QPHY_V6_PCS_LOCK_DETECT_CONFIG6' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_LOCK_DETECT_CONFIG6'? > > > > > > > > 994 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_LOCK_DETECT_CONFIG6, 0x13), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:997:26: error: 'QPHY_V6_PCS_RCVR_DTCT_DLY_P1U2_L' undeclared here (not in a function); did you mean 'QPHY_V3_PCS_RCVR_DTCT_DLY_P1U2_L'? > > > > > > > > 997 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_RCVR_DTCT_DLY_P1U2_L, 0xe7), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:998:26: error: 'QPHY_V6_PCS_RCVR_DTCT_DLY_P1U2_H' undeclared here (not in a function); did you mean 'QPHY_V3_PCS_RCVR_DTCT_DLY_P1U2_H'? > > > > > > > > 998 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_RCVR_DTCT_DLY_P1U2_H, 0x03), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:999:26: error: 'QPHY_V6_PCS_CDR_RESET_TIME' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_CDR_RESET_TIME'? > > > > > > > > 999 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_CDR_RESET_TIME, 0x0a), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1000:26: error: 'QPHY_V6_PCS_ALIGN_DETECT_CONFIG1' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_ALIGN_DETECT_CONFIG1'? > > > > > > > > 1000 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_ALIGN_DETECT_CONFIG1, 0x88), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1001:26: error: 'QPHY_V6_PCS_ALIGN_DETECT_CONFIG2' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_ALIGN_DETECT_CONFIG2'? > > > > > > > > 1001 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_ALIGN_DETECT_CONFIG2, 0x13), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1003:26: error: 'QPHY_V6_PCS_EQ_CONFIG1' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_EQ_CONFIG1'? > > > > > > > > 1003 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_EQ_CONFIG1, 0x4b), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1004:26: error: 'QPHY_V6_PCS_EQ_CONFIG5' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_EQ_CONFIG5'? > > > > > > > > 1004 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_EQ_CONFIG5, 0x10), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1008:26: error: 'QPHY_V6_PCS_USB3_LFPS_DET_HIGH_COUNT_VAL' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_USB3_LFPS_DET_HIGH_COUNT_VAL'? > > > > > > > > 1008 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_USB3_LFPS_DET_HIGH_COUNT_VAL, 0xf8), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1009:26: error: 'QPHY_V6_PCS_USB3_RXEQTRAINING_DFE_TIME_S2' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_USB3_RXEQTRAINING_DFE_TIME_S2'? > > > > > > > > 1009 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_USB3_RXEQTRAINING_DFE_TIME_S2, 0x07), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1010:26: error: 'QPHY_V6_PCS_USB3_RCVR_DTCT_DLY_U3_L' undeclared here (not in a function); did you mean 'QPHY_V4_PCS_USB3_RCVR_DTCT_DLY_U3_L'? > > > > > > > > 1010 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_USB3_RCVR_DTCT_DLY_U3_L, 0x40), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:1011:26: error: 'QPHY_V6_PCS_USB3_RCVR_DTCT_DLY_U3_H' undeclared here (not in a function); did you mean 'QPHY_V5_PCS_USB3_RCVR_DTCT_DLY_U3_H'? > > > > > > > > 1011 | QMP_PHY_INIT_CFG(QPHY_V6_PCS_USB3_RCVR_DTCT_DLY_U3_H, 0x00), > > > > > > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > drivers/phy/qualcomm/phy-qcom-qmp-usb.c:78:27: note: in definition of macro 'QMP_PHY_INIT_CFG' > > > > > > > > 78 | .offset = o, \ > > > > > > > > | ^ > > > > > > > > > > > > > > > > Caused by commit > > > > > > > > > > > > > > > > 685dbd1b2306 ("phy: qcom-qmp-usb: Add Qualcomm SDX75 USB3 PHY support") > > > > > > > > > > > > > > > > I have used the usb tree from next-20231003 for today. > > > > > > > Thanks, I've now reverted this from my tree. > > > > > > As mentioned in the cover letter of these changes, the series was dependent > > > > > > on the other submitted series [1], [2]. > > > > > Ah, I missed that, I almost never read cover letters :) > > > > > > > > > > > Can you also pick these series [1], [2] to resolve this build failures. > > > > > > [1] https://lore.kernel.org/all/20230911203842.778411-1-dmitry.baryshkov@linaro.org/ > > > > > > [2] https://lore.kernel.org/linux-phy/20230824211952.1397699-1-dmitry.baryshkov@linaro.org/ > > > > > How about you just send this change with these others, or all of them as > > > > > one big series so they can be applied in the proper order? > > > > Adding Dmitry as well. > > > > > > > > I see some of the dependent patches are already applied and the patches from > > > > [2] are not. > > > > Since all the rest dependent changes are already applied, > > > > you can pick series[2] and then this series that should also be fine. > > > > Please let me know if this is fine? > > > What is "this" series? I don't have any of these in my inbox at all > > > anymore, sorry. Please resend the pending patches that need to be > > > applied to my usb tree and I will be glad to do so. > > Actually, I wonder why the PHY patches were merged through the USB > > tree, maybe that is the issue here. > Yes Actually these patches needs to go via phy tree. Can you please drop > patch 1/5, 2/5 and 5/5 > from the series [3] (keeping [1] and [2] same reference from above to avoid > confusion). > > [3] https://lore.kernel.org/all/1695359525-4548-1-git-send-email-quic_rohiagar@quicinc.com/ > > At the same time requesting Vinod to please pick the patches 1/5, 2/5 and > 5/5 from series [3] and series [2]. I'm sorry, I have no idea what you need/want from me here. If there are patches that need to be reverted from my tree, please send reverts, I can't "drop" anything as my tree can not be rewritten. thanks, greg k-h