From: Tom Rini <trini@konsulko.com>
To: chaochao2021666@163.com
Cc: sjg@chromium.org, chao.zeng@siemens.com, baocheng.su@siemens.com,
jan.kiszka@siemens.com, u-boot@lists.denx.de
Subject: Re: [PATCH] gpio: da8xx_gpio: Fix gpio name with address
Date: Mon, 17 Jan 2022 13:37:28 -0500 [thread overview]
Message-ID: <20220117183728.GG2631111@bill-the-cat> (raw)
In-Reply-To: <20220107032624.1778421-1-chaochao2021666@163.com>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
On Fri, Jan 07, 2022 at 11:26:24AM +0800, chaochao2021666@163.com wrote:
> From: chao zeng <chao.zeng@siemens.com>
>
> The GPIO bank numbers do not appear in the device tree,
> so make the gpio name based on the address
> (ie gpio@42110000_25 vs 25)
>
> Signed-off-by: chao zeng <chao.zeng@siemens.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-01-17 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 3:26 [PATCH] gpio: da8xx_gpio: Fix gpio name with address chaochao2021666
2022-01-17 18:37 ` Tom Rini [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=20220117183728.GG2631111@bill-the-cat \
--to=trini@konsulko.com \
--cc=baocheng.su@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=chaochao2021666@163.com \
--cc=jan.kiszka@siemens.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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