From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [GIT PULL] pinctrl: renesas: Updates for v6.15 (take two)
Date: Thu, 13 Mar 2025 09:56:52 +0100 [thread overview]
Message-ID: <CACRpkdYcOsLt5zr+MokehEDiej6W7fWsj4UkLJ38nwJ+FMcKLQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1741362226.git.geert+renesas@glider.be>
On Fri, Mar 7, 2025 at 4:47 PM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> for you to fetch changes up to abcdeb4e299a11ecb5a3ea0cce00e68e8f540375:
>
> pinctrl: renesas: rza2: Fix missing of_node_put() call (2025-03-06 16:41:46 +0100)
Pulled in, thanks Geert!
Yours,
Linus Walleij
prev parent reply other threads:[~2025-03-13 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 15:47 [GIT PULL] pinctrl: renesas: Updates for v6.15 (take two) Geert Uytterhoeven
2025-03-13 8:56 ` Linus Walleij [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=CACRpkdYcOsLt5zr+MokehEDiej6W7fWsj4UkLJ38nwJ+FMcKLQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.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 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).