All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	<arm@kernel.org>,
	soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: mvebu: dt for v5.19 (#1)
Date: Fri, 13 May 2022 15:16:51 +0200	[thread overview]
Message-ID: <87lev5r2rg.fsf@BL-laptop> (raw)

Hi,

Here is the first pull request for dt for mvebu for v5.19.

Gregory

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt-5.19-1

for you to fetch changes up to f60e2de515095d04a05c6fc169ab6457bc70f3da:

  ARM: dts: turris-omnia: Add atsha204a node (2022-05-13 14:33:03 +0200)

----------------------------------------------------------------
mvebu dt for 5.19 (part 1)

Add the crypto module atsha204a node for the turis omnia (Armada 385 bases)

----------------------------------------------------------------
Pali Rohár (1):
      ARM: dts: turris-omnia: Add atsha204a node

 arch/arm/boot/dts/armada-385-turris-omnia.dts | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	<arm@kernel.org>,
	soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: mvebu: dt for v5.19 (#1)
Date: Fri, 13 May 2022 15:16:51 +0200	[thread overview]
Message-ID: <87lev5r2rg.fsf@BL-laptop> (raw)

Hi,

Here is the first pull request for dt for mvebu for v5.19.

Gregory

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt-5.19-1

for you to fetch changes up to f60e2de515095d04a05c6fc169ab6457bc70f3da:

  ARM: dts: turris-omnia: Add atsha204a node (2022-05-13 14:33:03 +0200)

----------------------------------------------------------------
mvebu dt for 5.19 (part 1)

Add the crypto module atsha204a node for the turis omnia (Armada 385 bases)

----------------------------------------------------------------
Pali Rohár (1):
      ARM: dts: turris-omnia: Add atsha204a node

 arch/arm/boot/dts/armada-385-turris-omnia.dts | 6 +++++-
 1 file changed, 5 insertions(+), 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-05-13 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 13:16 Gregory CLEMENT [this message]
2022-05-13 13:16 ` [GIT PULL] ARM: mvebu: dt for v5.19 (#1) Gregory CLEMENT
2022-05-13 21:40 ` 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=87lev5r2rg.fsf@BL-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=sebastian.hesselbarth@gmail.com \
    --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.