soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: soc@kernel.org, Tony Lindgren <tony@atomide.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 3/3] Changes for am3 cpsw and SanCloud for v5.15
Date: Thu, 12 Aug 2021 23:05:45 +0200	[thread overview]
Message-ID: <162880206192.1376011.3718743864242008546.b4-ty@arndb.de> (raw)
In-Reply-To: <pull-1628751694-126144@atomide.com-3>

From: Arnd Bergmann <arnd@arndb.de>

On Thu, 12 Aug 2021 10:03:44 +0300, Tony Lindgren wrote:
> The following changes since commit 8c054cd2818ea08555efe24a2ffde330833c2f3f:
> 
>   ARM: dts: am57xx: Add PRUSS MDIO controller nodes (2021-08-03 15:25:14 +0300)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.15/dt-am3-signed
> 
> [...]

Merged into arm/dt, thanks!

merge commit: 81b6a285737700c2e04ef0893617b80481b6b4b7

       Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: soc@kernel.org, Tony Lindgren <tony@atomide.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 3/3] Changes for am3 cpsw and SanCloud for v5.15
Date: Thu, 12 Aug 2021 23:05:45 +0200	[thread overview]
Message-ID: <162880206192.1376011.3718743864242008546.b4-ty@arndb.de> (raw)
Message-ID: <20210812210545.LmEKzQfcV6Wx08b-VqjUcTBSqmMjcX27Uisv32q14RM@z> (raw)
In-Reply-To: <pull-1628751694-126144@atomide.com-3>

From: Arnd Bergmann <arnd@arndb.de>

On Thu, 12 Aug 2021 10:03:44 +0300, Tony Lindgren wrote:
> The following changes since commit 8c054cd2818ea08555efe24a2ffde330833c2f3f:
> 
>   ARM: dts: am57xx: Add PRUSS MDIO controller nodes (2021-08-03 15:25:14 +0300)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.15/dt-am3-signed
> 
> [...]

Merged into arm/dt, thanks!

merge commit: 81b6a285737700c2e04ef0893617b80481b6b4b7

       Arnd

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

  parent reply	other threads:[~2021-08-12 21:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  7:03 [GIT PULL 1/3] Two missed omap Kconfig patches for v5.15 Tony Lindgren
2021-08-12  7:03 ` Tony Lindgren
2021-08-12  7:03 ` [GIT PULL 2/3] Drop pm_runtime_irq_safe() for smartreflex " Tony Lindgren
2021-08-12  7:03   ` Tony Lindgren
2021-08-12  7:54   ` Tony Lindgren
2021-08-12  7:54     ` Tony Lindgren
2021-08-12 20:44   ` Arnd Bergmann
2021-08-12 20:44     ` Arnd Bergmann
2021-08-12  7:03 ` [GIT PULL 3/3] Changes for am3 cpsw and SanCloud " Tony Lindgren
2021-08-12  7:03   ` Tony Lindgren
2021-08-12 21:05   ` Arnd Bergmann [this message]
2021-08-12 21:05     ` Arnd Bergmann
2021-08-12 20:41 ` [GIT PULL 1/3] Two missed omap Kconfig patches " Arnd Bergmann
2021-08-12 20:41   ` 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=162880206192.1376011.3718743864242008546.b4-ty@arndb.de \
    --to=arnd@kernel.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=soc@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;
as well as URLs for NNTP newsgroup(s).