From: Matthias Brugger <matthias.bgg@gmail.com> To: soc@kernel.org Cc: Josef Friedl <josef.friedl@speed.at>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@lists.infradead.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: [GIT PULL] ARM: dts32 updates for v5.5 Date: Mon, 11 Nov 2019 13:20:53 +0100 [thread overview] Message-ID: <82f16220-d0e1-6e32-088e-c889ef6bdff3@gmail.com> (raw) Hi Olof and Arnd, Please take the following pull-request into account. Thanks a lot, Matthias --- The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/ tags/v5.4-next-dts for you to fetch changes up to 4ab88db095c3a2ebbd6108cafcf327326f989ff8: arm: dts: mt6323: add keys, power-controller, rtc and codec (2019-11-10 21:39:44 +0100) ---------------------------------------------------------------- mt6323 pmic: add nodes for RTC, keys, codec and power-controller ---------------------------------------------------------------- Josef Friedl (1): arm: dts: mt6323: add keys, power-controller, rtc and codec arch/arm/boot/dts/mt6323.dtsi | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com> To: soc@kernel.org Cc: Josef Friedl <josef.friedl@speed.at>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@lists.infradead.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: [GIT PULL] ARM: dts32 updates for v5.5 Date: Mon, 11 Nov 2019 13:20:53 +0100 [thread overview] Message-ID: <82f16220-d0e1-6e32-088e-c889ef6bdff3@gmail.com> (raw) Hi Olof and Arnd, Please take the following pull-request into account. Thanks a lot, Matthias --- The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/ tags/v5.4-next-dts for you to fetch changes up to 4ab88db095c3a2ebbd6108cafcf327326f989ff8: arm: dts: mt6323: add keys, power-controller, rtc and codec (2019-11-10 21:39:44 +0100) ---------------------------------------------------------------- mt6323 pmic: add nodes for RTC, keys, codec and power-controller ---------------------------------------------------------------- Josef Friedl (1): arm: dts: mt6323: add keys, power-controller, rtc and codec arch/arm/boot/dts/mt6323.dtsi | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-11 12:21 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-11 12:20 Matthias Brugger [this message] 2019-11-11 12:20 ` [GIT PULL] ARM: dts32 updates for v5.5 Matthias Brugger
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=82f16220-d0e1-6e32-088e-c889ef6bdff3@gmail.com \ --to=matthias.bgg@gmail.com \ --cc=josef.friedl@speed.at \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=soc@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 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.