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 5BF22C77B73 for ; Thu, 20 Apr 2023 08:11:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234195AbjDTILE (ORCPT ); Thu, 20 Apr 2023 04:11:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231458AbjDTILD (ORCPT ); Thu, 20 Apr 2023 04:11:03 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E2D2173A; Thu, 20 Apr 2023 01:11:03 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 94573645CB; Thu, 20 Apr 2023 08:11:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3371AC433D2; Thu, 20 Apr 2023 08:11:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1681978262; bh=cRkJJtkBCNc6QMnaPnruYpRLA9mN0/qvOe5piHP2PL0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KwyuRbNTuY014OIygJWopqNWMjjzNCDieFS4GhXJ2NSLsERU+0C9VWL2CWYisnvjb R0Djg8vlgNA6K+bSAsN1QAztj87ny2HdQkF3o14W2QbblQUdKKMV0sFP3AIACuKpOh n1c8YZX7x9fW2TdV06CoYnVQo8Rr6CKHZjLrBx68= Date: Thu, 20 Apr 2023 10:10:58 +0200 From: Greg KH To: Shawn Guo Cc: Peng Fan , "Peng Fan (OSS)" , "robh+dt@kernel.org" , "krzysztof.kozlowski+dt@linaro.org" , "s.hauer@pengutronix.de" , Xu Yang , "kernel@pengutronix.de" , "festevam@gmail.com" , dl-linux-imx , "linux-usb@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Jun Li Subject: Re: [PATCH V7 10/10] ARM64: dts: imx7ulp: update usb compatible Message-ID: References: <20230322052504.2629429-1-peng.fan@oss.nxp.com> <20230322052504.2629429-11-peng.fan@oss.nxp.com> <20230405130649.GA11367@dragon> <20230406014013.GJ11367@dragon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230406014013.GJ11367@dragon> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, Apr 06, 2023 at 09:40:13AM +0800, Shawn Guo wrote: > On Thu, Apr 06, 2023 at 01:18:43AM +0000, Peng Fan wrote: > > Hi Shawn, > > > > > Subject: Re: [PATCH V7 10/10] ARM64: dts: imx7ulp: update usb compatible > > > > > > On Wed, Mar 22, 2023 at 01:25:04PM +0800, Peng Fan (OSS) wrote: > > > > From: Peng Fan > > > > > > > > Per binding doc, update the compatible > > > > > > > > Signed-off-by: Peng Fan > > > > > > ARM: dts: imx7ulp: ... > > > > > > Fixed it up and applied all DTS patches. > > [Peng Fan] > > > > Thanks for the fix. But I think Greg already applied the patchset. > > Okay, I will drop them from my tree, but ... > > Greg, > > May I suggest a couple of things on the future process? > > - Could you leave i.MX DTS patches to me, so that we can avoid potential > merge conflicts? How am I supposed to know this? Our tools take the whole patch series, not individual ones. If someone wants patches to go through different trees, then they need to submit them as different patch series, otherwise it makes no sense. > - Would you update your patch robot to reply the applying message to all > recipients, so that everyone knows the status? Can't really do that, it only responds to those that are on the patch signed-off-by list itself, as the other cc: metadata is gone after the patch is applied. thanks, greg k-h