From: Jisheng Zhang <Jisheng.Zhang@synaptics.com> To: soc@kernel.org, arm@kernel.org Cc: linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] berlin dts32 changes for 5.11 Date: Fri, 11 Dec 2020 10:05:21 +0800 [thread overview] Message-ID: <20201211100521.2e6f4faa@xhacker.debian> (raw) Hi Arnd, Kevin, Olof, Here is the dts32 changes for berlin for v5.11. Please kindly pull. thanks The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec: Linux 5.10-rc1 (2020-10-25 15:14:11 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jszhang/linux-berlin.git tags/v5.11-berlin-dts for you to fetch changes up to 7706e376f5311487099f5243875bf608347c915f: ARM: dts: berlin: Use generic "ngpios" rather than "snps,nr-gpios" (2020-12-10 17:50:11 +0800) ---------------------------------------------------------------- v5.11-berlin-dts ---------------------------------------------------------------- Alexander Dahl (1): ARM: dts: berlin: Fix schema warnings for pwm-leds Jisheng Zhang (1): ARM: dts: berlin: Use generic "ngpios" rather than "snps,nr-gpios" arch/arm/boot/dts/berlin2.dtsi | 12 ++++++------ arch/arm/boot/dts/berlin2cd-google-chromecast.dts | 6 +++--- arch/arm/boot/dts/berlin2cd.dtsi | 12 ++++++------ arch/arm/boot/dts/berlin2q.dtsi | 12 ++++++------ 4 files changed, 21 insertions(+), 21 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com> To: soc@kernel.org, arm@kernel.org Cc: linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] berlin dts32 changes for 5.11 Date: Fri, 11 Dec 2020 10:05:21 +0800 [thread overview] Message-ID: <20201211100521.2e6f4faa@xhacker.debian> (raw) Message-ID: <20201211020521.CtT-yMomf1hI2jamCQK6N4NkyqxL1-CvOIG6XPVwqUs@z> (raw) Hi Arnd, Kevin, Olof, Here is the dts32 changes for berlin for v5.11. Please kindly pull. thanks The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec: Linux 5.10-rc1 (2020-10-25 15:14:11 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jszhang/linux-berlin.git tags/v5.11-berlin-dts for you to fetch changes up to 7706e376f5311487099f5243875bf608347c915f: ARM: dts: berlin: Use generic "ngpios" rather than "snps,nr-gpios" (2020-12-10 17:50:11 +0800) ---------------------------------------------------------------- v5.11-berlin-dts ---------------------------------------------------------------- Alexander Dahl (1): ARM: dts: berlin: Fix schema warnings for pwm-leds Jisheng Zhang (1): ARM: dts: berlin: Use generic "ngpios" rather than "snps,nr-gpios" arch/arm/boot/dts/berlin2.dtsi | 12 ++++++------ arch/arm/boot/dts/berlin2cd-google-chromecast.dts | 6 +++--- arch/arm/boot/dts/berlin2cd.dtsi | 12 ++++++------ arch/arm/boot/dts/berlin2q.dtsi | 12 ++++++------ 4 files changed, 21 insertions(+), 21 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-11 2:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-11 2:05 Jisheng Zhang [this message] 2020-12-11 2:05 ` [GIT PULL] berlin dts32 changes for 5.11 Jisheng Zhang 2021-01-15 17:24 ` Arnd Bergmann 2021-01-15 17:24 ` Arnd Bergmann
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=20201211100521.2e6f4faa@xhacker.debian \ --to=jisheng.zhang@synaptics.com \ --cc=arm@kernel.org \ --cc=linux-arm-kernel@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.