From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Petar Stepanovic" <pstepanovic@axiado.com>,
"Akhila Kavi" <akavi@axiado.com>,
"Prasad Bolisetty" <pbolisetty@axiado.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Harshit Shah" <hshah@axiado.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] iio: adc: add Axiado SARADC driver
Date: Mon, 17 Aug 2026 13:56:10 +0200 [thread overview]
Message-ID: <20260817135610.00000c0c@gmail.com> (raw)
In-Reply-To: <anoYDi-bt-t6ZeeD@ashevche-desk.local>
On Mon, 10 Aug 2026 21:27:26 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
> > + soc_data = device_get_match_data(dev);
> > + if (!soc_data)
> > + return dev_err_probe(dev, -EINVAL, "failed to get match data\n");
>
> -ENODATA
Hmmm, I always thought it should be -ENODEV. (`grep -Rb5a5 "device_get_match_data"
drivers/iio/` confirms this, but maybe it's just wrong to begin with, a few
instances even have checks missing).
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-08-17 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 14:49 [PATCH v5 0/2] iio: adc: Add Axiado SARADC driver Petar Stepanovic
2026-08-10 14:49 ` [PATCH v5 1/2] dt-bindings: iio: adc: add Axiado AX3000/AX3005 SARADC Petar Stepanovic
2026-08-10 14:49 ` [PATCH v5 2/2] iio: adc: add Axiado SARADC driver Petar Stepanovic
2026-08-10 14:58 ` sashiko-bot
2026-08-10 18:27 ` Andy Shevchenko
2026-08-17 2:45 ` Jonathan Cameron
2026-08-17 11:59 ` Joshua Crofts
2026-08-17 11:56 ` Joshua Crofts [this message]
2026-08-17 13:05 ` Andy Shevchenko
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=20260817135610.00000c0c@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=akavi@axiado.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=hshah@axiado.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pbolisetty@axiado.com \
--cc=pstepanovic@axiado.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.