All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 0/4] ARM: SoC tree changes for 5.18
Date: Mon, 04 Apr 2022 13:05:47 +0000	[thread overview]
Message-ID: <164907754736.14449.6819635642624250498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CAK8P3a29JCfCNWrJ-x7S+kewcSBpeguyo8fmUTt_V4gfrW3=HA@mail.gmail.com>

Hello:

This series was applied to soc/soc.git (arm/fixes)
by Linus Torvalds <torvalds@linux-foundation.org>:

On Thu, 24 Mar 2022 00:05:17 +0100 you wrote:
> These are the usual four branches for 5.18, no late branch or other
> changes are pending this time. The contents are fairly typical, but
> there are nine new SoCs that are now supported in DT files, plus
> another one that only made it in partially.
> 
> The code changes in arch/arm/ are mainly cleanups, removing old
> board files and broken support for MMU-less kernels on systems
> that have an MMU.
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/4] ARM: defconfig updates for 5.18
    https://git.kernel.org/soc/soc/c/8ffa5709e577
  - [GIT,PULL,2/4] ARM: SoC updates for 5.18
    https://git.kernel.org/soc/soc/c/baaa68a9796e
  - [GIT,PULL,3/4] ARM: driver updates for 5.18
    https://git.kernel.org/soc/soc/c/b4bc93bd76d4
  - [GIT,PULL,4/4] ARM: DT updates for 5.18
    https://git.kernel.org/soc/soc/c/ed4643521e6a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-04-04 13:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 23:05 [GIT PULL 0/4] ARM: SoC tree changes for 5.18 Arnd Bergmann
2022-03-23 23:05 ` Arnd Bergmann
2022-03-23 23:08 ` [GIT PULL 1/4] ARM: defconfig updates " Arnd Bergmann
2022-03-23 23:08   ` Arnd Bergmann
2022-03-23 23:09   ` [GIT PULL 2/4] ARM: SoC " Arnd Bergmann
2022-03-23 23:09     ` Arnd Bergmann
2022-03-24  2:04     ` pr-tracker-bot
2022-03-24  2:04       ` pr-tracker-bot
2022-03-23 23:10   ` [GIT PULL 3/4] ARM: driver " Arnd Bergmann
2022-03-23 23:10     ` Arnd Bergmann
2022-03-24  2:04     ` pr-tracker-bot
2022-03-24  2:04       ` pr-tracker-bot
2022-03-23 23:12   ` [GIT PULL 4/4] ARM: DT " Arnd Bergmann
2022-03-23 23:12     ` Arnd Bergmann
2022-03-24  1:41     ` Linus Torvalds
2022-03-24  1:41       ` Linus Torvalds
2022-03-24  2:04     ` pr-tracker-bot
2022-03-24  2:04       ` pr-tracker-bot
2022-03-24  2:04   ` [GIT PULL 1/4] ARM: defconfig " pr-tracker-bot
2022-03-24  2:04     ` pr-tracker-bot
2022-04-04 13:05 ` patchwork-bot+linux-soc [this message]

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=164907754736.14449.6819635642624250498.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=arnd@kernel.org \
    --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.