Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Arnd <arnd@arndb.de>, Olof <olof@lixom.net>, SoC <soc@kernel.org>
Cc: <arm@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Tony Lindgren <tony@atomide.com>
Subject: [GIT PULL] ARM: dts: ti: keystone: Updates for v6.9
Date: Mon, 4 Mar 2024 07:38:43 -0600	[thread overview]
Message-ID: <20240304133843.e6rm5va6w4oavgoy@posted> (raw)

Hi Arnd, SoC team,

Apologies on a extremely late PR due to unavoidable personal
circumstances. This is very minor change, and would be nice to have in
v6.9. If it is too late, I can carry this forward for 6.10.

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-keystone-dt-for-v6.9

for you to fetch changes up to 11621bedc016578e0b025b6f23458e9fe3f3caad:

  ARM: dts: keystone: Replace http urls with https (2024-02-05 08:50:55 -0600)

----------------------------------------------------------------
Keystone2 device tree updates for v6.9

Cosmetic cleanups:
* Replace http urls with https.

----------------------------------------------------------------
Nishanth Menon (1):
      ARM: dts: keystone: Replace http urls with https

 arch/arm/boot/dts/ti/keystone/keystone-clocks.dtsi      | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2e-clocks.dtsi  | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2e-evm.dts      | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2e-netcp.dtsi   | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2e.dtsi         | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2g-evm.dts      | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2g-ice.dts      | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2g-netcp.dtsi   | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2g.dtsi         | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2hk-clocks.dtsi | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2hk-evm.dts     | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2hk-netcp.dtsi  | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2hk.dtsi        | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2l-clocks.dtsi  | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2l-evm.dts      | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2l-netcp.dtsi   | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone-k2l.dtsi         | 2 +-
 arch/arm/boot/dts/ti/keystone/keystone.dtsi             | 2 +-
 18 files changed, 18 insertions(+), 18 deletions(-)
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2024-03-04 13:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240304133843.e6rm5va6w4oavgoy@posted \
    --to=nm@ti.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 \
    --cc=ssantosh@kernel.org \
    --cc=tony@atomide.com \
    /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: link
Be 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