From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: Branch for GPIO hard numbers removal
Date: Wed, 17 May 2023 09:21:35 +0300 [thread overview]
Message-ID: <20230517062135.GM14287@atomide.com> (raw)
In-Reply-To: <CACRpkdY5xoLm_Wi6-FJ3UPqmo6Zfbfp+ePUyL-BtVg_a7NFh9w@mail.gmail.com>
Hi,
* Linus Walleij <linus.walleij@linaro.org> [230516 12:15]:
> Hi Tony,
>
> I have this branch for removing all hardcoded GPIO numbers
> in OMAP1 and OMAP2 (3):
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/log/?h=gpio-descriptors-omap
Yes great to see all those changes in a branch, looks really nice
to me. No need to go tweak the branch, but if you end up needing
to update it for some reason, feel free to add for all changes:
Reviewed-by: Tony Lindgren <tony@atomide.com>
> Most stuff relating to other subsystems have proper ACKs from
> the subsystem maintainers.
>
> Is this something you want to pull into the OMAP tree?
No need for me to send it AFAIK..
> Or do you want me to send a pull request directly to the SoC
> tree (with your ACK, if you ACK it).
..yes please do. This should not conflict with anything, please go
ahead and send the pull request yourself. I can always merge it in
if needed.
> It needs some rotation in linux-next so we can smoke out any
> remaining bugs.
Sounds good to me.
Regards,
Tony
_______________________________________________
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:[~2023-05-17 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 12:15 Branch for GPIO hard numbers removal Linus Walleij
2023-05-17 6:21 ` Tony Lindgren [this message]
2023-05-17 20:56 ` Aaro Koskinen
2023-05-17 21:44 ` Linus Walleij
2023-05-17 21:46 ` Linus Walleij
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=20230517062135.GM14287@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).