From: David Lechner <dlechner@baylibre.com>
To: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>, "Chris Hall" <c-hall@ti.com>,
"Patrick Edwards" <pedwards@ti.com>,
"Kurt Borja" <kuurtb@gmail.com>,
"Nguyen Minh Tien" <zizuzacker@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] iio: adc: ti-ads112c14: add debugfs register access
Date: Wed, 22 Jul 2026 17:52:41 -0500 [thread overview]
Message-ID: <c8bd955b-1d1f-40e1-bede-82e5e9a7bde8@baylibre.com> (raw)
In-Reply-To: <20260720012446.27f0411b@jic23-huawei>
On 7/19/26 7:24 PM, Jonathan Cameron wrote:
> On Tue, 14 Jul 2026 19:19:30 -0500
> "David Lechner (TI)" <dlechner@baylibre.com> wrote:
>
>> Add debugfs register access to the ads112c14 driver. This is a complex
>> chip and being able to poke registers is useful for debugging and
>> diagnostic/calibration purposes.
>>
>> Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
> Given this one is trivial, applied.
Did this get dropped or just not pushed out yet?
>
> Jonathan
>
next prev parent reply other threads:[~2026-07-22 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 0:19 [PATCH 0/3] iio: adc: ti-ads112c14: buffered read support David Lechner (TI)
2026-07-15 0:19 ` [PATCH 1/3] iio: adc: ti-ads112c14: add debugfs register access David Lechner (TI)
2026-07-20 0:24 ` Jonathan Cameron
2026-07-22 22:52 ` David Lechner [this message]
2026-07-23 23:18 ` Jonathan Cameron
2026-07-15 0:19 ` [PATCH 2/3] iio: adc: ti-ads112c14: add support for I2C CRC8 David Lechner (TI)
2026-07-20 0:35 ` Jonathan Cameron
2026-07-15 0:19 ` [PATCH 3/3] iio: adc: ti-ads112c14: add support for buffered read David Lechner (TI)
2026-07-20 0:55 ` Jonathan Cameron
2026-07-21 23:23 ` David Lechner
2026-07-23 23:25 ` Jonathan Cameron
2026-07-24 14:47 ` David Lechner
2026-07-24 21:34 ` 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=c8bd955b-1d1f-40e1-bede-82e5e9a7bde8@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=c-hall@ti.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kuurtb@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pedwards@ti.com \
--cc=zizuzacker@gmail.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®