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 89883C4167D for ; Mon, 28 Nov 2022 14:51:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231491AbiK1OvG (ORCPT ); Mon, 28 Nov 2022 09:51:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42752 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229775AbiK1OvE (ORCPT ); Mon, 28 Nov 2022 09:51:04 -0500 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4FA9D2253A; Mon, 28 Nov 2022 06:51:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1669647061; x=1701183061; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wtpNKUl602erZp5JhGLEdS/fNX0dwgMjE2H5qtJYc2s=; b=DCSKmWV9qgqGX6IDlQRyTNSmgL/1VTxs6vLmQq88jLKJCiB0P6sVFqYz d226XBNMh3JDEilcQXOPGSSFhGXx7WnjQIKsvTpsTOLSVvcaSCYTErtbH e2BnFY7p6EUyHCr9t2DYA9vp7KajCuFJdwFVzr0mKDXPx/Qtx6bUewG+w dY5aQleaJ0Yg1l5Ln5ALNq1swj9JjwnEVRO891kgCwnWMFsKpxnWd1eRS dNywSSOSreKrYrs2EXf4akjNny8HWUv3eaYudtx/GqLnugDMxat0sVwfz /wIIcE2/idZsg5t+cSVG8RQr5P2xmDD8ENjqYnw4FBph91kliJxXCef32 g==; X-IronPort-AV: E=Sophos;i="5.96,200,1665471600"; d="scan'208";a="188967090" Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 28 Nov 2022 07:51:00 -0700 Received: from chn-vm-ex04.mchp-main.com (10.10.85.152) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12; Mon, 28 Nov 2022 07:50:59 -0700 Received: from wendy (10.10.115.15) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12 via Frontend Transport; Mon, 28 Nov 2022 07:50:57 -0700 Date: Mon, 28 Nov 2022 14:50:39 +0000 From: Conor Dooley To: Jisheng Zhang CC: Conor Dooley , Rob Herring , Krzysztof Kozlowski , Paul Walmsley , Palmer Dabbelt , Albert Ou , Greg Kroah-Hartman , Jiri Slaby , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , , , , Subject: Re: [PATCH v2 8/9] MAINTAINERS: riscv: add entry for Bouffalolab SoC Message-ID: References: <20221127132448.4034-1-jszhang@kernel.org> <20221127132448.4034-9-jszhang@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Jisheng, On Mon, Nov 28, 2022 at 10:30:08PM +0800, Jisheng Zhang wrote: > Per my past experience of synaptics/mrvl arm SoCs, I usually sent PRs to Arnd > if there are two or more commits/patches; If there's only one patch, I > asked Arnd for picking it up directly. So in bouffalolab SoC case, I > want to do similar, but with one difference -- if there's only one > patch, may I ask you for picking it up directly? Works for me :) Unless I hear otherwise on a given patch, I'll assume you've got it taken care of. > > > git tree here. Otherwise, LMK and I'll bundle it with the other "misc > > Hmm, is "git tree" necessary? If you have one that you're sending PRs from, it's nice to know what/where someone that may have a patch for your stuff can base their changes on. You don't need to obviously. Thanks! Conor.