From: Alex Elder <elder@riscstar.com>
To: Linus Walleij <linusw@kernel.org>, Bartosz Golaszewski <brgl@kernel.org>
Cc: Michael Walle <mwalle@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v2 0/2] Improvement spotted during patch review.
Date: Mon, 11 May 2026 07:18:51 -0500 [thread overview]
Message-ID: <e12be7b2-a24e-44a6-9a4f-9a90ab950d17@riscstar.com> (raw)
In-Reply-To: <CAD++jLkG35pTLY2=vyj974PjDax277ebqYd_WUjLOeQHEvntsw@mail.gmail.com>
On 5/11/26 7:15 AM, Linus Walleij wrote:
> On Mon, May 11, 2026 at 11:56 AM Bartosz Golaszewski <brgl@kernel.org> wrote:
>> On Fri, May 8, 2026 at 2:51 PM Linus Walleij <linusw@kernel.org> wrote:
>>>
>>> Support sparse unidirectional GPIO lines.
>>>
>>> To be used in a forthcoming submission.
>>
>> Should I apply it or will Alex just include it in his series?
>
> I think it's easiest if you just apply it then Alex can just base his
> patch series off your for-next branch (or cherry-pick those
> underneath his patch series).
>
> Yours,
> Linus Walleij
I'm good with that plan. -Alex
next prev parent reply other threads:[~2026-05-11 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 12:51 [PATCH v2 0/2] Improvement spotted during patch review Linus Walleij
2026-05-08 12:51 ` [PATCH v2 1/2] gpio: regmap: Support sparsed fixed direction Linus Walleij
2026-05-08 13:03 ` Alex Elder
2026-05-10 13:31 ` Alex Elder
2026-05-11 7:18 ` Michael Walle
2026-05-11 19:00 ` Linus Walleij
2026-05-08 12:51 ` [PATCH v2 2/2] gpio: regmap: Don't set a fixed direction line Linus Walleij
2026-05-11 7:24 ` Michael Walle
2026-05-11 9:56 ` [PATCH v2 0/2] Improvement spotted during patch review Bartosz Golaszewski
2026-05-11 12:15 ` Linus Walleij
2026-05-11 12:18 ` Alex Elder [this message]
2026-05-11 12:32 ` Bartosz Golaszewski
2026-05-11 12:39 ` Michael Walle
2026-05-11 12:44 ` 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=e12be7b2-a24e-44a6-9a4f-9a90ab950d17@riscstar.com \
--to=elder@riscstar.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=sashiko-bot@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