All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Linus Walleij <linus.walleij@linaro.org>
Cc: soc@kernel.org
Subject: Re: [PATCH] ARM: dts: gpio-ranges property is now required
Date: Sat, 08 Jan 2022 22:00:10 +0000	[thread overview]
Message-ID: <164167921063.24856.5272264509238287957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220104170247.956760-1-linus.walleij@linaro.org>

Hello:

This patch was applied to soc/soc.git (arm/fixes)
by Olof Johansson <olof@lixom.net>:

On Tue,  4 Jan 2022 18:02:47 +0100 you wrote:
> From: Phil Elwell <phil@raspberrypi.com>
> 
> Since [1], added in 5.7, the absence of a gpio-ranges property has
> prevented GPIOs from being restored to inputs when released.
> Add those properties for BCM283x and BCM2711 devices.
> 
> [1] commit 2ab73c6d8323 ("gpio: Support GPIO controllers without
>     pin-ranges")
> 
> [...]

Here is the summary with links:
  - ARM: dts: gpio-ranges property is now required
    https://git.kernel.org/soc/soc/c/c8013355ead6

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-01-08 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 17:02 [PATCH] ARM: dts: gpio-ranges property is now required Linus Walleij
2022-01-04 17:02 ` Linus Walleij
2022-01-04 21:57 ` Florian Fainelli
2022-01-04 21:57   ` Florian Fainelli
2022-01-08 21:04 ` Stefan Wahren
2022-01-08 21:04   ` Stefan Wahren
2022-01-08 21:18   ` Olof Johansson
2022-01-08 21:18     ` Olof Johansson
2022-01-08 22:00 ` 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=164167921063.24856.5272264509238287957.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=linus.walleij@linaro.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.