From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Jones, Carlos jr" <Carlosjr.Jones@analog.com>,
Andy Shevchenko <andy@kernel.org>,
"Sa, Nuno" <Nuno.Sa@analog.com>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Liam Beguin <liambeguin@gmail.com>,
"Marques, Jorge" <Jorge.Marques@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v2 0/2] iio: adc: ltc2309: Add LTC2305 read delay and optimize chip_info
Date: Sun, 12 Apr 2026 16:49:39 +0100 [thread overview]
Message-ID: <20260412164939.068cbe9a@jic23-huawei> (raw)
In-Reply-To: <4c34f4f3-f3c0-403e-bf14-29403ce263b8@baylibre.com>
On Sat, 11 Apr 2026 13:48:05 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 4/10/26 9:27 PM, Jones, Carlos jr wrote:
> >>> This series adds missing read delay support for the LTC2305 and
> >>> optimizes the chip_info structure for better memory safety and efficiency.
> >>>
> >>> The LTC2305 requires a 1.6μs delay between I2C channel selection and
> >>> data read operations - a timing requirement identified by the hardware
> >>> designer that wasn't captured in the initial LTC2305 support (commit
> >>> 8625d418d24b ("iio: adc: ltc2309: add support for ltc2305")).
> >>>
> >>> Additionally, the chip_info structure is enhanced with
> >>> __counted_by_ptr() annotation for improved bounds checking and
> >>> reorganized to minimize padding.
> >>
> >> Now LGTM,
> >> Reviewed-by: Andy Shevchenko <andy@kernel.org>
> >>
> >> --
> >> With Best Regards,
> >> Andy Shevchenko
> >
> >>
> >> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
> >
> > Thank you for the review, Andy and Nuno.
> >
> > Hi Jonathan,
> >
> > Just a gentle ping on this series, it has received reviews from Andy and Nuno.
> > Let me know if there’s anything else needed from my side.
> >
> > Kind regards,
> > Carlos
>
> FYI, Jonathan uses patchwork, so you can see the status of the patch
> at https://patchwork.kernel.org/project/linux-iio/list/.
>
> If it still says "New", then it is still in the queue and hasn't
> been forgotten. There is usually a lull after the -rc6 release
> until the next -rc1 release. Then things start moving at a normal
> pace again. So it still might a be a few weeks before this gets
> picked up.
+ over 2 weeks is convention before reminders... Life gets busy sometimes.
On this occasion I was on holiday - blame Delta cancelling my flight back
for making it a slightly longer holiday than planned!
May take me a week or so to get back on top of things.
https://lore.kernel.org/all/20260323112729.00003715@huawei.com/
As noted we are very close to the merge window anyway so I'm only queuing
up for next cycle now and nothing will hit linux-next until after rc1.
Applied to the testing branch of iio.git.
thanks,
Jonathan
next prev parent reply other threads:[~2026-04-12 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 1:24 [PATCH v2 0/2] iio: adc: ltc2309: Add LTC2305 read delay and optimize chip_info Carlos Jones Jr
2026-03-31 1:24 ` [PATCH v2 1/2] iio: adc: ltc2309: add read delay for ltc2305 Carlos Jones Jr
2026-03-31 1:24 ` [PATCH v2 2/2] iio: adc: ltc2309: Optimize chip_info structure layout Carlos Jones Jr
2026-03-31 7:01 ` [PATCH v2 0/2] iio: adc: ltc2309: Add LTC2305 read delay and optimize chip_info Andy Shevchenko
2026-04-11 2:27 ` Jones, Carlos jr
2026-04-11 18:48 ` David Lechner
2026-04-12 15:49 ` Jonathan Cameron [this message]
2026-04-13 1:36 ` Jones, Carlos jr
2026-03-31 10:44 ` Nuno Sá
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=20260412164939.068cbe9a@jic23-huawei \
--to=jic23@kernel.org \
--cc=Carlosjr.Jones@analog.com \
--cc=Jorge.Marques@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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