Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp348212ybm; Fri, 29 May 2020 01:30:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwdP4jdHAnnTqSZD0tVk9SdPaVTvtyTpJjc+kG9ECaHj0AfoGEKiaZUVrXVrxxSHikJBj1W X-Received: by 2002:a05:6402:17f9:: with SMTP id t25mr7220120edy.134.1590741055650; Fri, 29 May 2020 01:30:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590741055; cv=none; d=google.com; s=arc-20160816; b=rtT2b3AI3wgIbbOXB4mQpflh+TkwUsFNuOkN5fhfhRfJk0pRcLkAviecAR/0OA3k6C fVkTQvM3ODW2JQTPAjYz0EDek1HbAxK1KhU2I9xBCWPibaioiHO1pAwZpf/Mll3Wq6OE FknopKbUoGxSnGshZZL/J7XTKt79deb9kZ8S/HcpGcHYUgeY8Bd+eLdY+XEqbOe/l7te UwqDXOituzQXLer482/Nkh0q2ghpvzOAzbq24W+3jvTqUgpPikkplgO+h77hlye81Cqj 0Ln6wLZZcubSfGviWEfO6i6GzZQWhc62lO5HtFjUgsBTM3gbqXuRzvRddBrK73zITwx8 LonQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=IDO/7VtP+P7m9JLpy/1xbSd9do5gkCPNFtRecniB8ac=; b=XV4cPH1N80IXCXI3k2W5UEqkabmtx1bTqYjFCMcKJvZfFL00t8iEw5pvTkHANC+uxT 6zd4UPlGwzPc+E4B3ZV6WscdqZN/mT1GpjkXHKSNzQJQ4YYBXGdj2HTiyMDgmkMv4XPV V5PB3eFOigzfx2/MykK8LMlKPhe22FtCt+ELPjHJtygnp4BRklQJ7/MU+91+77EkP9fY kn9mwc8oDGAqPMVQgYrf+x2KC8jtArNa31It4o7ZApy/VR8yYVgg/9n5ajBZW5afwMJE nY7UhMCV3j6i8nipqmXIHzs0N+fzGt6nbhfr8RVzQ5iiHabE+fITPaFDdmPf6+v+ybGz Ndqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=cm6HZccZ; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=JYMoNcLX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cm22si395453edb.370.2020.05.29.01.30.32; Fri, 29 May 2020 01:30:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=cm6HZccZ; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=JYMoNcLX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725939AbgE2I2p (ORCPT + 99 others); Fri, 29 May 2020 04:28:45 -0400 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:59929 "EHLO wout3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725775AbgE2I2o (ORCPT ); Fri, 29 May 2020 04:28:44 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 71A817EE; Fri, 29 May 2020 04:28:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 29 May 2020 04:28:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=IDO/7VtP+P7m9JLpy/1xbSd9do5 gkCPNFtRecniB8ac=; b=cm6HZccZHihiheMoZ4Qp1TTaNv7eGQdBaXJ0E1tpQSz RyNKkIyYFswYcHsKJGnhndScInrtgl9P2ixqKNG1WDpp3CvSQj48bh7SrA/k3fg0 qGC380Gul2GQi658FVDT3/3ra4g1rznwOWjzqU/CmGPrJTFoVLmcFmt5eDMof+CS JDFe+WY/SPZxAGjdRk3AHDo5RWtNFoaYxiOZJ9ntVSKyMq3eAePe3z+Sj493hLLq BGsktSlq7xViyfbVk9dQtUHg9mecvhn4tr95EXasqursZm3EBG0QA3XV6Yb2eewX U//5Nh3xCdK+pkQ0TaqopgXFaCunFjZUkU30lc/+OpQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=IDO/7V tP+P7m9JLpy/1xbSd9do5gkCPNFtRecniB8ac=; b=JYMoNcLXzyk/gqQmcM6AJA NxT9i/FNbkkZN7cVyw5uZDVtulqMbKboMnw+cZD1yh+iE6Q988Da/VncYij747M8 9kATkdqtOQv8+p/LjahroG3+MXf7IVGLZq7bEIaG7JvPwntl6EfW/f21Wq1Yryhw J5Vr2eDC26itXyavfTmwlODBNctl0YYXReSAQR3WIaaNkPPsqcW+/sRR3IPFKDB4 koDI36+YJRypw0dbA5N9WBWMxSLyneYa9X451tMMF/WAkJEO36Se264p8gLtSiTc DoGQpZAIYREyYIN5KNLdcVjfC2QD85WtXn/NYIUiCLxdkHwaB9lQ3YQyyzBM8BKw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddvkedgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeevueehje fgfffgiedvudekvdektdelleelgefhleejieeugeegveeuuddukedvteenucfkphepkeef rdekiedrkeelrddutdejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 70DD73280060; Fri, 29 May 2020 04:28:42 -0400 (EDT) Date: Fri, 29 May 2020 10:28:40 +0200 From: Greg KH To: Rob Herring Cc: Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List , Sandeep Maheswaram , Felipe Balbi Subject: Re: linux-next: manual merge of the usb tree with the devicetree tree Message-ID: <20200529082840.GC847132@kroah.com> References: <20200528162215.3a9aa663@canb.auug.org.au> <20200528104916.GD3115014@kroah.com> <20200529082641.GB847132@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200529082641.GB847132@kroah.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 29, 2020 at 10:26:41AM +0200, Greg KH wrote: > On Thu, May 28, 2020 at 08:14:36AM -0600, Rob Herring wrote: > > On Thu, May 28, 2020 at 4:49 AM Greg KH wrote: > > > > > > On Thu, May 28, 2020 at 04:22:15PM +1000, Stephen Rothwell wrote: > > > > Hi all, > > > > > > > > Today's linux-next merge of the usb tree got a conflict in: > > > > > > > > Documentation/devicetree/bindings/usb/qcom,dwc3.yaml > > > > > > > > between commit: > > > > > > > > 3828026c9ec8 ("dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings") > > > > > > > > from the devicetree tree and commits: > > > > > > > > cd4b54e2ae1f ("dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings") > > > > > > > > from the usb tree. > > > > > > > > I fixed it up (I guessed, taking most changes from the former) and can > > > > carry the fix as necessary. This is now fixed as far as linux-next is > > > > concerned, but any non trivial conflicts should be mentioned to your > > > > upstream maintainer when your tree is submitted for merging. You may > > > > also want to consider cooperating with the maintainer of the > > > > conflicting tree to minimise any particularly complex conflicts. > > > > Ugg, I fixed up a warning on my side... > > > > > > > > Sounds good,t hanks. > > > > Greg, can you revert your copy and we can get rid of the conflict. > > I can, if you also add the attached patch to your tree, as it was a > follow-on one from the original one and I had to revert it too. Also this one as well. --------------------- From b88035625ec9594d4554a307e820aef4b759e35f Mon Sep 17 00:00:00 2001 From: Sandeep Maheswaram Date: Thu, 26 Mar 2020 12:36:08 +0530 Subject: [PATCH] dt-bindings: usb: qcom,dwc3: Add compatible for SC7180 Add compatible for SC7180 in usb dwc3 bindings. Signed-off-by: Sandeep Maheswaram Reviewed-by: Douglas Anderson Acked-by: Rob Herring Reviewed-by: Stephen Boyd Signed-off-by: Felipe Balbi diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml index 0f69475566c7..17e22ff528dd 100644 --- a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml @@ -16,6 +16,7 @@ properties: - enum: - qcom,msm8996-dwc3 - qcom,msm8998-dwc3 + - qcom,sc7180-dwc3 - qcom,sdm845-dwc3 - const: qcom,dwc3