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 alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4672CC61DA4 for ; Fri, 3 Feb 2023 08:39:38 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 31C1285D; Fri, 3 Feb 2023 09:38:46 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 31C1285D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1675413576; bh=/PA5B2UfTLW8o56P3800UFEzmzZSk6ZCDfweudu2H5U=; h=Date:From:To:Subject:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=Qdcu3ptU8ISPmObUX7Wywi535goj37nbPAHt1TMAwrrJFB6wkyDY8BQxip04zNOg3 PyHXN8TFhsx6D07QAtm5yzyCfcTCh7TnPuhx7yRL9k6uBJffuE6beCWiIPYB3PRJqV O2hcEuIN5AKt5Sk1aTPt8zFYbaXWpFUkWHSEe1pc= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 5A4BDF80543; Fri, 3 Feb 2023 09:37:56 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 49F1FF8032B; Fri, 3 Feb 2023 09:30:45 +0100 (CET) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 276B2F800E3 for ; Fri, 3 Feb 2023 09:30:40 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 276B2F800E3 Received: by verein.lst.de (Postfix, from userid 2407) id 494A367373; Fri, 3 Feb 2023 09:30:38 +0100 (CET) Date: Fri, 3 Feb 2023 09:30:37 +0100 From: Christoph Hellwig To: John Paul Adrian Glaubitz Subject: Re: remove arch/sh Message-ID: <20230203083037.GA30738@lst.de> References: <20230113062339.1909087-1-hch@lst.de> <11e2e0a8-eabe-2d8c-d612-9cdd4bcc3648@physik.fu-berlin.de> <20230116071306.GA15848@lst.de> <40dc1bc1-d9cd-d9be-188e-5167ebae235c@physik.fu-berlin.de> <20230203071423.GA24833@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Mailman-Approved-At: Fri, 03 Feb 2023 09:37:52 +0100 X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-fbdev@vger.kernel.org, Rich Felker , Geert Uytterhoeven , linux-sh@vger.kernel.org, linux-rtc@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org, Christoph Hellwig , linux-arch@vger.kernel.org, Yoshinori Sato , linux-serial@vger.kernel.org, linux-input@vger.kernel.org, linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org, Arnd Bergmann , linux-gpio@vger.kernel.org, Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Kieran Bingham , netdev@vger.kernel.org, dmaengine@vger.kernel.org, alsa-devel@alsa-project.org, Laurent Pinchart Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote: > Since this is my very first time stepping up as a kernel maintainer, I was hoping > to get some pointers on what to do to make this happen. > > So far, we have set up a new kernel tree and I have set up a local development and > test environment for SH kernels using my SH7785LCR board as the target platform. > > Do I just need to send a patch asking to change the corresponding entry in the > MAINTAINERS file? I'm not sure a there is a document, but: - add the MAINTAINERS change to your tree - ask Stephen to get your tree included in linux-next then eventually send a pull request to Linus with all of that. Make sure it's been in linux-next for a while. 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 C3EACC63797 for ; Fri, 3 Feb 2023 08:30:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231923AbjBCIas (ORCPT ); Fri, 3 Feb 2023 03:30:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39638 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230144AbjBCIar (ORCPT ); Fri, 3 Feb 2023 03:30:47 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 380503D0B7; Fri, 3 Feb 2023 00:30:44 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 494A367373; Fri, 3 Feb 2023 09:30:38 +0100 (CET) Date: Fri, 3 Feb 2023 09:30:37 +0100 From: Christoph Hellwig To: John Paul Adrian Glaubitz Cc: Christoph Hellwig , Yoshinori Sato , Rich Felker , Arnd Bergmann , Greg Kroah-Hartman , Laurent Pinchart , Kieran Bingham , Geert Uytterhoeven , linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, linux-arch@vger.kernel.org, dmaengine@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org, linux-input@vger.kernel.org, linux-media@vger.kernel.org, linux-mmc@vger.kernel.org, linux-mtd@lists.infradead.org, netdev@vger.kernel.org, linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org, linux-spi@vger.kernel.org, linux-serial@vger.kernel.org, linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org, alsa-devel@alsa-project.org, linux-sh@vger.kernel.org Subject: Re: remove arch/sh Message-ID: <20230203083037.GA30738@lst.de> References: <20230113062339.1909087-1-hch@lst.de> <11e2e0a8-eabe-2d8c-d612-9cdd4bcc3648@physik.fu-berlin.de> <20230116071306.GA15848@lst.de> <40dc1bc1-d9cd-d9be-188e-5167ebae235c@physik.fu-berlin.de> <20230203071423.GA24833@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote: > Since this is my very first time stepping up as a kernel maintainer, I was hoping > to get some pointers on what to do to make this happen. > > So far, we have set up a new kernel tree and I have set up a local development and > test environment for SH kernels using my SH7785LCR board as the target platform. > > Do I just need to send a patch asking to change the corresponding entry in the > MAINTAINERS file? I'm not sure a there is a document, but: - add the MAINTAINERS change to your tree - ask Stephen to get your tree included in linux-next then eventually send a pull request to Linus with all of that. Make sure it's been in linux-next for a while. 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D4B94C61DA4 for ; Fri, 3 Feb 2023 08:30:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=T7o+dm3k7RK8rcrchoiw1n1CWX/ciVTcJ34xA98Am6E=; b=H62n/mdDy7Oe09 /GEv0wPkSyTxUjIONFp/m8Wri8McZHXZITUD/4Ci7kezn3txoGnA0Do9WdVzTuPmumsQgRDMOWcUm Ggp6PJQ1wT6yL2N1/mOYnPctE6ZdeRbhmImimBu7CTWJjQrv7tj7S429FYgjObttvtbCEQezowYYI IeZJrjHUjPdinjw6fro0XsyHQLLKyHW0nq+TOAAuwki+j/WmZEG7oYJwRnoYL2VIf1MeW81ERZ2HE XXVw0lldyd8wvj3Sk7j4KNxTdMhkbSUMLAHO/xLq7Fo0bUjp3AUcDWdaBmu4Lqj3/hRrB6oJvYqUi UjHhAHPmfrNUKOTXGLsQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pNrTA-0011py-DM; Fri, 03 Feb 2023 08:30:52 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pNrT7-0011oB-Hz for linux-mtd@lists.infradead.org; Fri, 03 Feb 2023 08:30:50 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id 494A367373; Fri, 3 Feb 2023 09:30:38 +0100 (CET) Date: Fri, 3 Feb 2023 09:30:37 +0100 From: Christoph Hellwig To: John Paul Adrian Glaubitz Cc: Christoph Hellwig , Yoshinori Sato , Rich Felker , Arnd Bergmann , Greg Kroah-Hartman , Laurent Pinchart , Kieran Bingham , Geert Uytterhoeven , linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, linux-arch@vger.kernel.org, dmaengine@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org, linux-input@vger.kernel.org, linux-media@vger.kernel.org, linux-mmc@vger.kernel.org, linux-mtd@lists.infradead.org, netdev@vger.kernel.org, linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org, linux-spi@vger.kernel.org, linux-serial@vger.kernel.org, linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org, alsa-devel@alsa-project.org, linux-sh@vger.kernel.org Subject: Re: remove arch/sh Message-ID: <20230203083037.GA30738@lst.de> References: <20230113062339.1909087-1-hch@lst.de> <11e2e0a8-eabe-2d8c-d612-9cdd4bcc3648@physik.fu-berlin.de> <20230116071306.GA15848@lst.de> <40dc1bc1-d9cd-d9be-188e-5167ebae235c@physik.fu-berlin.de> <20230203071423.GA24833@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230203_003049_756569_E8296420 X-CRM114-Status: GOOD ( 20.23 ) X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-mtd" Errors-To: linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org On Fri, Feb 03, 2023 at 09:24:46AM +0100, John Paul Adrian Glaubitz wrote: > Since this is my very first time stepping up as a kernel maintainer, I was hoping > to get some pointers on what to do to make this happen. > > So far, we have set up a new kernel tree and I have set up a local development and > test environment for SH kernels using my SH7785LCR board as the target platform. > > Do I just need to send a patch asking to change the corresponding entry in the > MAINTAINERS file? I'm not sure a there is a document, but: - add the MAINTAINERS change to your tree - ask Stephen to get your tree included in linux-next then eventually send a pull request to Linus with all of that. Make sure it's been in linux-next for a while. ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/