All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>
Cc: soc@kernel.org
Subject: Re: [PATCH v2 0/3] PL022 DT fixes for seattle, lg and lpc platform
Date: Fri, 11 Mar 2022 10:50:10 +0000	[thread overview]
Message-ID: <164699581051.25725.6706762400815957104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220311093800.18778-1-singh.kuldeep87k@gmail.com>

Hello:

This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Fri, 11 Mar 2022 15:07:57 +0530 you wrote:
> This patchset is an attempt to fix DTs which are not compliant with
> pl022 spi binding. Please note, there are other fixes required also
> which are sent from other trees.
> As git trees for these platforms are not available, Rob advised me to
> seek help from soc tree maintainers.
> 
> Arnd and Olof, could you please help in reviewing and merging this
> patchset.
> 
> [...]

Here is the summary with links:
  - [v2,1/3] arm64: dts: seattle: Update spi clock properties
    https://git.kernel.org/soc/soc/c/2201faa9fd72
  - [v2,2/3] arm64: dts: lg131x: Update spi clock properties
    https://git.kernel.org/soc/soc/c/19297aab805a
  - [v2,3/3] ARM: dts: lpc32xx: Update spi clock properties
    https://git.kernel.org/soc/soc/c/dc89633b8a1c

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-03-11 10:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  9:37 [PATCH v2 0/3] PL022 DT fixes for seattle, lg and lpc platform Kuldeep Singh
2022-03-11  9:37 ` Kuldeep Singh
2022-03-11  9:37 ` [PATCH v2 1/3] arm64: dts: seattle: Update spi clock properties Kuldeep Singh
2022-03-11  9:37   ` Kuldeep Singh
2022-03-11  9:37 ` [PATCH v2 2/3] arm64: dts: lg131x: " Kuldeep Singh
2022-03-11  9:37   ` Kuldeep Singh
2022-03-11  9:38 ` [PATCH v2 3/3] ARM: dts: lpc32xx: " Kuldeep Singh
2022-03-11  9:38   ` Kuldeep Singh
2022-03-11 13:20   ` Vladimir Zapolskiy
2022-03-11 13:20     ` Vladimir Zapolskiy
2022-03-11 13:38     ` Arnd Bergmann
2022-03-11 13:38       ` Arnd Bergmann
2022-03-11 14:07       ` Vladimir Zapolskiy
2022-03-11 14:07         ` Vladimir Zapolskiy
2022-03-11 14:33         ` Krzysztof Kozlowski
2022-03-11 14:33           ` Krzysztof Kozlowski
2022-03-11 21:26           ` Vladimir Zapolskiy
2022-03-11 21:26             ` Vladimir Zapolskiy
2022-03-12 10:23             ` Krzysztof Kozlowski
2022-03-12 10:23               ` Krzysztof Kozlowski
2022-03-12 12:26               ` Vladimir Zapolskiy
2022-03-12 12:26                 ` Vladimir Zapolskiy
2022-03-14 11:43         ` Robin Murphy
2022-03-14 11:43           ` Robin Murphy
2022-03-14 11:50           ` Vladimir Zapolskiy
2022-03-14 11:50             ` Vladimir Zapolskiy
2022-03-14 12:20             ` Robin Murphy
2022-03-14 12:20               ` Robin Murphy
2022-03-14 12:32               ` Arnd Bergmann
2022-03-14 12:32                 ` Arnd Bergmann
2022-03-14 17:55                 ` Robin Murphy
2022-03-14 17:55                   ` Robin Murphy
2022-03-14 12:34               ` Vladimir Zapolskiy
2022-03-14 12:34                 ` Vladimir Zapolskiy
2022-03-27  2:57                 ` Trevor Woerner
2022-03-27 16:27                   ` Vladimir Zapolskiy
2022-03-27 16:27                     ` Vladimir Zapolskiy
2022-03-27 18:32                     ` Trevor Woerner
2022-03-27 18:32                       ` Trevor Woerner
2022-03-11 10:50 ` 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=164699581051.25725.6706762400815957104.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=singh.kuldeep87k@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.