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: Fri, 18 Jul 2025 11:23:46 +0200 [thread overview]
Message-ID: <cb913a0a-0f3f-4890-aa1f-1b01ec9c564e@kernel.org> (raw)
In-Reply-To: <c947d537-cae5-44f0-abd8-0c558bac46d2@csgroup.eu>
On 10/07/2025 08:44, Christophe Leroy wrote:
> Hi Arnd,
>
> Please pull the following Freescale Soc Drivers changes for 6.17
>
> The tegra change is outside soc/fsl tree but it is acked by maintainer
> of DRM DRIVERS FOR NVIDIA TEGRA.
>
> Thanks
> Christophe
>
> The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
>
> Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
>
> are available in the Git repository at:
>
> https://github.com/chleroy/linux.git tags/soc_fsl-6.17-1
>
> for you to fetch changes up to 76760b9dbbf8088ef31afb60d92b955f88ad1288:
>
> soc: Use dev_fwnode() (2025-07-08 10:29:28 +0200)
>
> ----------------------------------------------------------------
> FSL SOC Changes for 6.17:
> - Use dev_fwnode() instead of of_fwnode_handle()
> - 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).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-18 9: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 [this message]
2025-07-30 6:10 ` Christophe Leroy
2025-07-30 6:23 ` Krzysztof Kozlowski
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=cb913a0a-0f3f-4890-aa1f-1b01ec9c564e@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
all inboxes | Powered by JetHome®