From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] IIO: New device support, features and cleanup for 7.0
Date: Mon, 2 Feb 2026 17:07:32 +0100 [thread overview]
Message-ID: <2026020249-neurotic-resolved-aad7@gregkh> (raw)
In-Reply-To: <20260201165951.481378da@jic23-huawei>
On Sun, Feb 01, 2026 at 04:59:51PM +0000, Jonathan Cameron wrote:
> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
>
> Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-7.0a
>
> for you to fetch changes up to 0713b26190addfa3a774b386c8658952ef9f7faf:
>
> iio: magn: mmc5633: Fix Kconfig for combination of I3C as module and driver builtin (2026-02-01 16:53:35 +0000)
>
> ----------------------------------------------------------------
> IIO: New device support, features and cleanup for the 6.20/7.0 cycle.
>
> Slightly messier than normal unfortunately due to some conflicts
> and build config bugs related to I3C drivers.
>
> One last minute Kconfig fix right at the top after a linux-next report.
> I've simplified the Kconfig and made it match other instances in the kernel
> so that should be safe enough despite short soak time in front of build bots.
>
> Merge of an immutable branch from I3C to get some stubs that were missing
> and caused build issues with dual I2C / I3C drivers. This also brought in a
> drop of some deprecated interfaces so there is also one patch to update a
> new driver to not use those.
>
> We are having another go at using cleanup.h magic with the IIO mode claim
> functions after backing out last try at this. This time we have wrappers
> around the new ACQUIRE() and ACQUIRE_ERR() macros.
> Having been burnt once, we will be taking it a bit more slowly this time
> wrt to wide adoption of these! Thanks in particular to Kurt for taking
> on this core IIO work.
I got a merge conflict in drivers/iio/adc/ad9467.c and resolved it this
way:
diff --cc drivers/iio/adc/ad9467.c
index 2d8f8da3671d,9cfe66425d4e..000000000000
--- a/drivers/iio/adc/ad9467.c
+++ b/drivers/iio/adc/ad9467.c
@@@ -94,8 -103,8 +103,8 @@@
*/
#define CHIPID_AD9434 0x6A
- #define AD9434_DEF_OUTPUT_MODE 0x00
+ #define AD9434_DEF_OUTPUT_MODE 0x01
-#define AD9434_REG_VREF_MASK 0xC0
+#define AD9434_REG_VREF_MASK GENMASK(4, 0)
/*
* Analog Devices AD9467 16-Bit, 200/250 MSPS ADC
Hopefully I did it right?
If not, can you send a fix-up patch for me?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-02 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 16:59 [PULL] IIO: New device support, features and cleanup for 7.0 Jonathan Cameron
2026-02-02 16:07 ` Greg KH [this message]
2026-02-02 17:41 ` Jonathan Cameron
2026-02-02 17:45 ` Tomas Melin
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=2026020249-neurotic-resolved-aad7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.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