From: "xingtong.wu" <xingtong_wu@163.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: brgl@bgdev.pl, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, henning.schild@siemens.com,
xingtong.wu@siemens.com
Subject: Re: [PATCH v2 1/1] gpio-f7188x: fix base values conflicts with other gpio pins
Date: Thu, 2 Mar 2023 21:48:57 +0800 [thread overview]
Message-ID: <7b8435c9-36ad-9b69-7357-94cb5fcadc99@163.com> (raw)
In-Reply-To: <CACRpkdaLyEmdhutqsMUoV3ObW8bFePtNGHFqr5qiKV3w0ripug@mail.gmail.com>
On 2023/5/29 21:02, Linus Walleij wrote:
> On Mon, May 29, 2023 at 4:55 AM <xingtong_wu@163.com> wrote:
>
>> From: "xingtong.wu" <xingtong.wu@siemens.com>
>>
>> switch pin base from static to automatic allocation to
>> avoid conflicts and align with other gpio chip drivers
>>
>> Signed-off-by: xingtong.wu <xingtong.wu@siemens.com>
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> If this platform does not have a ton of userspace using the obsolete
> sysfs this should be fine to apply. I say let's apply and see what happens.
>
> Yours,
> Linus Walleij
Hi
Seems it has been a while since our last discussion, I guess it might
be fit in.
-- XingTong Wu
next prev parent reply other threads:[~2023-07-20 3:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 2:50 [PATCH v2 0/1] " xingtong_wu
2023-05-29 2:50 ` [PATCH v2 1/1] " xingtong_wu
2023-05-29 12:26 ` simon.guinot
2023-05-29 13:03 ` Linus Walleij
2023-05-29 13:54 ` simon.guinot
2023-05-29 22:24 ` andy.shevchenko
2023-05-30 6:27 ` xingtong.wu
2023-05-30 10:53 ` andy.shevchenko
2023-05-30 11:10 ` andy.shevchenko
2023-05-30 17:53 ` simon.guinot
2023-05-30 21:42 ` Andy Shevchenko
2023-05-30 10:57 ` Henning Schild
2023-05-30 17:57 ` simon.guinot
2023-05-30 11:40 ` Linus Walleij
2023-05-29 13:02 ` Linus Walleij
2023-03-02 13:48 ` xingtong.wu [this message]
2023-06-16 7:53 ` Henning Schild
2023-08-31 7:28 ` xingtong.wu
2023-09-01 9:10 ` Bartosz Golaszewski
2023-09-11 7:04 ` Bartosz Golaszewski
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=7b8435c9-36ad-9b69-7357-94cb5fcadc99@163.com \
--to=xingtong_wu@163.com \
--cc=brgl@bgdev.pl \
--cc=henning.schild@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xingtong.wu@siemens.com \
/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
all inboxes | Powered by JetHome®