From: Santosh Shilimkar <santosh.shilimkar@oracle.com> To: arm@kernel.org, arnd@arndb.de, olof@lixom.net Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, santosh.shilimkar@oracle.com, soc@kernel.org Subject: [GIT PULL 2/2] ARM: DTS: Keystone update for v5.12 Date: Sun, 31 Jan 2021 21:21:50 -0800 [thread overview] Message-ID: <1612156910-11159-1-git-send-email-santosh.shilimkar@oracle.com> (raw) The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e: Linux 5.11-rc1 (2020-12-27 15:30:22 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone_dts_for_5.12 for you to fetch changes up to 091584182ba6a298351f1e555c13ceb880c1f397: arm: dts: keystone: Harmonize DWC USB3 DT nodes name (2021-01-24 20:50:48 -0800) ---------------------------------------------------------------- ARM: DTS: Keystone update for v5.12 Contains couple updates for DWC USB3 DT nodes ---------------------------------------------------------------- Serge Semin (2): arm: dts: keystone: Correct DWC USB3 compatible string arm: dts: keystone: Harmonize DWC USB3 DT nodes name arch/arm/boot/dts/keystone-k2e.dtsi | 6 +++--- arch/arm/boot/dts/keystone.dtsi | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@oracle.com> To: arm@kernel.org, arnd@arndb.de, olof@lixom.net Cc: soc@kernel.org, santosh.shilimkar@oracle.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [GIT PULL 2/2] ARM: DTS: Keystone update for v5.12 Date: Sun, 31 Jan 2021 21:21:50 -0800 [thread overview] Message-ID: <1612156910-11159-1-git-send-email-santosh.shilimkar@oracle.com> (raw) Message-ID: <20210201052150.wJ-iOk8TLvGotjDwp1KL9d0aOh0I9VnmPe3eGcjxHsM@z> (raw) The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e: Linux 5.11-rc1 (2020-12-27 15:30:22 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone_dts_for_5.12 for you to fetch changes up to 091584182ba6a298351f1e555c13ceb880c1f397: arm: dts: keystone: Harmonize DWC USB3 DT nodes name (2021-01-24 20:50:48 -0800) ---------------------------------------------------------------- ARM: DTS: Keystone update for v5.12 Contains couple updates for DWC USB3 DT nodes ---------------------------------------------------------------- Serge Semin (2): arm: dts: keystone: Correct DWC USB3 compatible string arm: dts: keystone: Harmonize DWC USB3 DT nodes name arch/arm/boot/dts/keystone-k2e.dtsi | 6 +++--- arch/arm/boot/dts/keystone.dtsi | 4 ++-- 2 files changed, 5 insertions(+), 5 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:[~2021-02-01 5:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-01 5:21 Santosh Shilimkar [this message] 2021-02-01 5:21 ` [GIT PULL 2/2] ARM: DTS: Keystone update for v5.12 Santosh Shilimkar 2021-02-02 17:10 ` Arnd Bergmann 2021-02-02 17:10 ` 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=1612156910-11159-1-git-send-email-santosh.shilimkar@oracle.com \ --to=santosh.shilimkar@oracle.com \ --cc=arm@kernel.org \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=olof@lixom.net \ --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.