From: Arnd Bergmann <arnd@kernel.org> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Bartosz Golaszewski <brgl@bgdev.pl>, Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>, ARM <linux-arm-kernel@lists.infradead.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux Next Mailing List <linux-next@vger.kernel.org>, Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp> Subject: Re: linux-next: manual merge of the gpio-brgl tree with the arm-soc tree Date: Tue, 9 Feb 2021 12:35:30 +0100 [thread overview] Message-ID: <CAK8P3a1Fv=Bei+Zkq43yn_dek=RB96_yXrtJ-ZA5K4nf06joOw@mail.gmail.com> (raw) In-Reply-To: <CAMuHMdWAOXpJGTRM7O7ix4uG-hpH-kDiueN51oA0YEZ0vJdZfw@mail.gmail.com> On Tue, Feb 9, 2021 at 11:01 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > On Thu, Jan 28, 2021 at 7:05 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > index 37da418393e0,950010a290f0..000000000000 > > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > @@@ -42,7 -42,6 +42,11 @@@ > > clock-names = "apb_pclk"; > > }; > > > > +&wdt { > > + status = "okay"; > > + clocks = <&wdt_clk>; > > +}; > > ++ > > + &gpio { > > + status = "okay"; > > + }; > > Probably some sort order should be taken into account (gpio before uart0), > also avoidng the conflict? > We normally do this by asking everyone to send the dts changes for inclusion through the soc tree rather than the subsystem that contains the driver. Why is this one in the gpio-brgl tree? Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>, Bartosz Golaszewski <brgl@bgdev.pl>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Linux Next Mailing List <linux-next@vger.kernel.org>, Olof Johansson <olof@lixom.net>, Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>, ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: linux-next: manual merge of the gpio-brgl tree with the arm-soc tree Date: Tue, 9 Feb 2021 12:35:30 +0100 [thread overview] Message-ID: <CAK8P3a1Fv=Bei+Zkq43yn_dek=RB96_yXrtJ-ZA5K4nf06joOw@mail.gmail.com> (raw) In-Reply-To: <CAMuHMdWAOXpJGTRM7O7ix4uG-hpH-kDiueN51oA0YEZ0vJdZfw@mail.gmail.com> On Tue, Feb 9, 2021 at 11:01 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > On Thu, Jan 28, 2021 at 7:05 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > index 37da418393e0,950010a290f0..000000000000 > > --- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > +++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts > > @@@ -42,7 -42,6 +42,11 @@@ > > clock-names = "apb_pclk"; > > }; > > > > +&wdt { > > + status = "okay"; > > + clocks = <&wdt_clk>; > > +}; > > ++ > > + &gpio { > > + status = "okay"; > > + }; > > Probably some sort order should be taken into account (gpio before uart0), > also avoidng the conflict? > We normally do this by asking everyone to send the dts changes for inclusion through the soc tree rather than the subsystem that contains the driver. Why is this one in the gpio-brgl tree? Arnd _______________________________________________ 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-02-09 11:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-28 6:03 linux-next: manual merge of the gpio-brgl tree with the arm-soc tree Stephen Rothwell 2021-01-28 6:03 ` Stephen Rothwell 2021-02-09 10:01 ` Geert Uytterhoeven 2021-02-09 10:01 ` Geert Uytterhoeven 2021-02-09 11:35 ` Arnd Bergmann [this message] 2021-02-09 11:35 ` Arnd Bergmann 2021-02-10 5:33 ` nobuhiro1.iwamatsu 2021-02-10 5:33 ` nobuhiro1.iwamatsu 2023-05-30 4:19 Stephen Rothwell 2023-05-30 4:19 ` Stephen Rothwell 2023-05-30 9:28 ` Arnd Bergmann 2023-05-30 9:28 ` Arnd Bergmann 2023-05-30 9:35 ` Bartosz Golaszewski 2023-05-30 9:35 ` Bartosz Golaszewski 2023-05-30 9:49 ` Linus Walleij 2023-05-30 9:49 ` Linus Walleij
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='CAK8P3a1Fv=Bei+Zkq43yn_dek=RB96_yXrtJ-ZA5K4nf06joOw@mail.gmail.com' \ --to=arnd@kernel.org \ --cc=arnd@arndb.de \ --cc=bgolaszewski@baylibre.com \ --cc=brgl@bgdev.pl \ --cc=geert@linux-m68k.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=nobuhiro1.iwamatsu@toshiba.co.jp \ --cc=olof@lixom.net \ --cc=sfr@canb.auug.org.au \ /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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.