From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
soc@kernel.org, Arnd Bergmann <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SOC FSL for 6.17
Date: Wed, 30 Jul 2025 08:23:39 +0200 [thread overview]
Message-ID: <fb454b30-9229-4095-91ba-62906d3bd276@kernel.org> (raw)
In-Reply-To: <b885d194-dee0-4cc8-ad85-25949baf02b3@csgroup.eu>
On 30/07/2025 08:10, Christophe Leroy wrote:
>>> - Use new GPIO line value setter callbacks
>>
>> It has been many days and I still do not see this patch in linux-next.
>> Please confirm that you properly feed linux-next and for how long this
>> patch was sitting there (BEFORE you send them to upstream maintainer).
>
> Until recently I was relying on my branch poping up into linux-next once
> merged into the soc tree.
>
> Since monday last week it is now included in linux-next independently.
>
Thank you!
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-30 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 6:44 Christophe Leroy
2025-07-18 9:23 ` Krzysztof Kozlowski
2025-07-30 6:10 ` Christophe Leroy
2025-07-30 6:23 ` Krzysztof Kozlowski [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=fb454b30-9229-4095-91ba-62906d3bd276@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@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
Powered by JetHome