From: Arnd Bergmann <arnd@kernel.org>
To: soc@kernel.org, olof@lixom.net,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Cc: bgolaszewski@baylibre.com, linus.walleij@linaro.org,
yuji2.ishikawa@toshiba.co.jp,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL] ARM: Visconti: device tree changes for 5.12
Date: Thu, 11 Feb 2021 16:04:22 +0100 [thread overview]
Message-ID: <161305573916.259289.1286171955086418832.b4-ty@arndb.de> (raw)
Message-ID: <20210211150422.IWdKD_Y2021AJESkoS2xkfnalPySTcv0pTTbm84EeCc@z> (raw)
In-Reply-To: <20210210173210.nnytfyrkkj6ylrtb@toshiba.co.jp>
From: Arnd Bergmann <arnd@arndb.de>
On Thu, 11 Feb 2021 02:32:10 +0900, Nobuhiro Iwamatsu wrote:
> This request includes the GPIO DT patch for the Visconti SoC.
> Please pull for v5.12 kernel cycle.
>
> The following changes since commit 4fd18fc38757217c746aa063ba9e4729814dc737:
>
> arm64: dts: visconti: Add watchdog support for TMPV7708 SoC (2021-01-25 09:20:47 +0900)
>
> are available in the Git repository at:
>
> [...]
Merged into arm/dt, thanks!
merge commit: a36c9ff6a2df17295e0050dc9a9d5abff4b21dd7
I see that the pull request is not a signed tag, please remember to
add a tag description and signature next time.
As the changes in here are all trivial, I pulled them anyway for
5.12.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-11 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 17:32 [GIT PULL] ARM: Visconti: device tree changes for 5.12 Nobuhiro Iwamatsu
2021-02-10 17:32 ` Nobuhiro Iwamatsu
2021-02-11 15:04 ` Arnd Bergmann [this message]
2021-02-11 15:04 ` Arnd Bergmann
2021-02-11 15:20 ` patchwork-bot+linux-soc
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=161305573916.259289.1286171955086418832.b4-ty@arndb.de \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=yuji2.ishikawa@toshiba.co.jp \
/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).