From: David Lechner <dlechner@baylibre.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Jonathan Cameron" <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Dumitru Ceclan <dumitru.ceclan@analog.com>,
Nuno Sa <nuno.sa@analog.com>,
Guillaume Ranquet <granquet@baylibre.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7124: Disable all channels at probe time
Date: Fri, 6 Dec 2024 09:35:15 -0600 [thread overview]
Message-ID: <276fcd4d-5066-46b8-8468-f63d35b74894@baylibre.com> (raw)
In-Reply-To: <7did4jkzbsvovlinkjimbn3zdqrwi2mrs2onukfonjeexnumvh@xbzcdad4v7kd>
On 12/6/24 5:04 AM, Uwe Kleine-König wrote:
> Hello Jonathan,
>
> On Sat, Nov 09, 2024 at 03:24:38PM +0000, Jonathan Cameron wrote:
>> Sadly this has probably missed 6.12, but I have queued it up as a fix
>> for early next cycle and marked it for stable.
>
> I interpreted "early next cycle" as "This will go into v6.13-rc1.". But
> that didn't work and didn't hit the mainline yet (as of cdd30ebb1b9f).
>
> This patch was included in next as
> 64612ec9b909b699293b7220c634f67a9fc12e06 between next-20241111 and
> next-20241128 and then disappeared from there.
>
> What is wrong here?
>
> Best regards
> Uwe
FYI, the iio tree is currently missing from linux-next due to [1].
[1]: https://lore.kernel.org/all/d707cb3b-1569-45d9-bdc3-dcc98eb88bc4@sirena.org.uk/
next prev parent reply other threads:[~2024-12-06 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 10:19 Uwe Kleine-König
2024-11-09 15:24 ` Jonathan Cameron
2024-12-06 11:04 ` Uwe Kleine-König
2024-12-06 15:35 ` David Lechner [this message]
2024-12-06 16:11 ` Uwe Kleine-König
2024-12-07 17:15 ` Jonathan Cameron
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=276fcd4d-5066-46b8-8468-f63d35b74894@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=dumitru.ceclan@analog.com \
--cc=granquet@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=u.kleine-koenig@baylibre.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®