All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <arnd@arndb.de>, <olof@lixom.net>, <arm@kernel.org>, <soc@kernel.org>
Cc: <nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] AT91 device tree updates for 6.2 #2
Date: Fri, 18 Nov 2022 15:12:14 +0200	[thread overview]
Message-ID: <20221118131214.301678-1-claudiu.beznea@microchip.com> (raw)

The following changes since commit 5258d30f33bdbb495f6de7601db5d60e13223a5b:

  ARM: dts: at91: sam9x60ek: remove status = "okay" for regulators (2022-11-01 12:28:58 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/at91-dt-6.2-2

for you to fetch changes up to 7a3c62678699d7e56736c2d0579d077a7773e77c:

  ARM: dts: at91: sama7g5: fix signal name of pin PD8 (2022-11-17 15:32:33 +0200)

----------------------------------------------------------------
AT91 DT for 6.2 #2

It contains:
- one typo fix for a SAMA7G5 pin; the pin is not used anywhere in the
  device trees.

----------------------------------------------------------------
Mihai Sain (1):
      ARM: dts: at91: sama7g5: fix signal name of pin PD8

 arch/arm/boot/dts/sama7g5-pinfunc.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

WARNING: multiple messages have this Message-ID (diff)
From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <arnd@arndb.de>, <olof@lixom.net>, <arm@kernel.org>, <soc@kernel.org>
Cc: alexandre.belloni@bootlin.com, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] AT91 device tree updates for 6.2 #2
Date: Fri, 18 Nov 2022 15:12:14 +0200	[thread overview]
Message-ID: <20221118131214.301678-1-claudiu.beznea@microchip.com> (raw)

The following changes since commit 5258d30f33bdbb495f6de7601db5d60e13223a5b:

  ARM: dts: at91: sam9x60ek: remove status = "okay" for regulators (2022-11-01 12:28:58 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/at91-dt-6.2-2

for you to fetch changes up to 7a3c62678699d7e56736c2d0579d077a7773e77c:

  ARM: dts: at91: sama7g5: fix signal name of pin PD8 (2022-11-17 15:32:33 +0200)

----------------------------------------------------------------
AT91 DT for 6.2 #2

It contains:
- one typo fix for a SAMA7G5 pin; the pin is not used anywhere in the
  device trees.

----------------------------------------------------------------
Mihai Sain (1):
      ARM: dts: at91: sama7g5: fix signal name of pin PD8

 arch/arm/boot/dts/sama7g5-pinfunc.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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

             reply	other threads:[~2022-11-18 13:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 13:12 Claudiu Beznea [this message]
2022-11-18 13:12 ` [GIT PULL] AT91 device tree updates for 6.2 #2 Claudiu Beznea
2022-11-21 14:52 ` patchwork-bot+linux-soc

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=20221118131214.301678-1-claudiu.beznea@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=nicolas.ferre@microchip.com \
    --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: link
Be 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.