From: Arnd Bergmann <arnd@kernel.org> To: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>, SoC Team <soc@kernel.org>, Will Deacon <will@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net> Subject: Re: Date: Fri, 8 Jan 2021 13:30:30 +0100 [thread overview] Message-ID: <CAK8P3a1TxK_+gX1wNBEi_h664YS2Nw57MECknbZEkZQRiuCQVw@mail.gmail.com> (raw) In-Reply-To: <20210108103227.1740865-1-misono.tomohiro@jp.fujitsu.com> On Fri, Jan 8, 2021 at 11:32 AM Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> wrote: > Subject: [RFC PATCH 00/10] Add Fujitsu A64FX soc entry/hardware barrier driver > [RFC] > This is the first time we upstream drivers for our chip and I want to > confirm driver location and patch submission process. > > Based on my observation it seems drivers/soc folder is right place to put > this driver, so I added Kconfig entry for arm64 platform config, created > soc/fujitsu folder and updated MAINTAINER entry accordingly (last patch). > Is it right? This looks good as a start. It may be possible that during review, we come up with a different location or a different user interface that may change the code, but if it stays in drivers/soc/fujitsu, then the other steps are absolutely right. > Also for final submission I think I need to 1) create some public git > tree to push driver code (github or something), 2) make pull request to > SOC team (soc@kernel.org). Is it a correct procedure? Yes. I would prefer something other than github, e.g. an account on a fujitsu.com host, on kernel.org, or on git.linaro.org, but github works if none of the alternatives are easy for you. When you send a pull request, make sure you sign the tag with a gpg key, ideally after getting it on the kernel.org keyring [1]. Arnd [1] https://korg.docs.kernel.org/pgpkeys.html
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org> To: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> Cc: Arnd Bergmann <arnd@arndb.de>, Catalin Marinas <catalin.marinas@arm.com>, SoC Team <soc@kernel.org>, Olof Johansson <olof@lixom.net>, Will Deacon <will@kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: Date: Fri, 8 Jan 2021 13:30:30 +0100 [thread overview] Message-ID: <CAK8P3a1TxK_+gX1wNBEi_h664YS2Nw57MECknbZEkZQRiuCQVw@mail.gmail.com> (raw) Message-ID: <20210108123030.EDgsjPlKSKSBiz9_mu8KmI8kjxF_7dh2NEnIu1cfhZ0@z> (raw) In-Reply-To: <20210108103227.1740865-1-misono.tomohiro@jp.fujitsu.com> On Fri, Jan 8, 2021 at 11:32 AM Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> wrote: > Subject: [RFC PATCH 00/10] Add Fujitsu A64FX soc entry/hardware barrier driver > [RFC] > This is the first time we upstream drivers for our chip and I want to > confirm driver location and patch submission process. > > Based on my observation it seems drivers/soc folder is right place to put > this driver, so I added Kconfig entry for arm64 platform config, created > soc/fujitsu folder and updated MAINTAINER entry accordingly (last patch). > Is it right? This looks good as a start. It may be possible that during review, we come up with a different location or a different user interface that may change the code, but if it stays in drivers/soc/fujitsu, then the other steps are absolutely right. > Also for final submission I think I need to 1) create some public git > tree to push driver code (github or something), 2) make pull request to > SOC team (soc@kernel.org). Is it a correct procedure? Yes. I would prefer something other than github, e.g. an account on a fujitsu.com host, on kernel.org, or on git.linaro.org, but github works if none of the alternatives are easy for you. When you send a pull request, make sure you sign the tag with a gpg key, ideally after getting it on the kernel.org keyring [1]. Arnd [1] https://korg.docs.kernel.org/pgpkeys.html _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-08 12:30 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-08 10:32 Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 01/10] soc: fujitsu: hwb: Add hardware barrier driver init/exit code Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 11:58 ` Jonathan Cameron 2021-01-08 11:58 ` Jonathan Cameron 2021-01-12 10:35 ` misono.tomohiro 2021-01-12 10:35 ` misono.tomohiro 2021-01-08 12:41 ` Arnd Bergmann 2021-01-08 12:41 ` Arnd Bergmann 2021-01-12 10:49 ` misono.tomohiro 2021-01-12 10:49 ` misono.tomohiro 2021-01-08 10:32 ` [PATCH 02/10] soc: fujtisu: hwb: Add open operation Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 03/10] soc: fujitsu: hwb: Add IOC_BB_ALLOC ioctl Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 04/10] soc: fujitsu: hwb: Add IOC_BW_ASSIGN ioctl Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 05/10] soc: fujitsu: hwb: Add IOC_BW_UNASSIGN ioctl Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 06/10] soc: fujitsu: hwb: Add IOC_BB_FREE ioctl Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 07/10] soc: fujitsu: hwb: Add IOC_GET_PE_INFO ioctl Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 08/10] soc: fujitsu: hwb: Add release operation Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 09/10] soc: fujitsu: hwb: Add sysfs entry Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 10:32 ` [PATCH 10/10] soc: fujitsu: hwb: Add Kconfig/Makefile to build fujitsu_hwb driver Misono Tomohiro 2021-01-08 10:32 ` Misono Tomohiro 2021-01-08 12:30 ` Arnd Bergmann [this message] 2021-01-08 12:30 ` Arnd Bergmann 2021-01-08 10:35 misono.tomohiro 2021-09-03 20:51 RE: Mr. James Khmalo 2023-05-30 1:31 RE; Olena Shevchenko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAK8P3a1TxK_+gX1wNBEi_h664YS2Nw57MECknbZEkZQRiuCQVw@mail.gmail.com \ --to=arnd@kernel.org \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=misono.tomohiro@jp.fujitsu.com \ --cc=olof@lixom.net \ --cc=soc@kernel.org \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).