From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
"Sa, Nuno" <Nuno.Sa@analog.com>,
Andy Shevchenko <andy@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI drivers
Date: Fri, 27 Feb 2026 16:48:46 +0200 [thread overview]
Message-ID: <aaGuzkHk6kCkcyiz@ashevche-desk.local> (raw)
In-Reply-To: <CY4PR03MB3399CFF77F5C0051731D64989B73A@CY4PR03MB3399.namprd03.prod.outlook.com>
On Fri, Feb 27, 2026 at 11:23:10AM +0000, Miclaus, Antoniu wrote:
> > -----Original Message-----
> > From: Andy Shevchenko <andriy.shevchenko@intel.com>
> > Sent: Wednesday, February 25, 2026 6:15 PM
> > On Wed, Feb 25, 2026 at 05:05:46PM +0200, Antoniu Miclaus wrote:
> > > Changes in v3:
> > > - Squash the struct device variable introduction and dev_err_probe()
> > > conversion into a single patch per driver.
> >
> > Why? Maybe my comment was unclear previous time.
> >
> > The idea is to convert to short dev the only lines that are not being touched
> > by the second (dev_err_probe() conversion) patch.
>
> Sure, so for the function which use dev only for the dev errors I introduce
> the struct device *dev = &spi->dev; in the dev_error_probe patch?
Whenever you use it first, there you introduce it. I believe in this case it
will in the first patch of each driver subseries. Whatever the first patch is.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-02-27 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 15:05 Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 1/6] iio: frequency: adrf6780: add dev variable and use dev_err_probe Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 2/6] iio: frequency: admv1014: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 3/6] iio: frequency: admv1013: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 4/6] iio: frequency: adf4377: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 5/6] iio: dac: ad7293: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 6/6] iio: filter: admv8818: " Antoniu Miclaus
2026-02-25 16:15 ` [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI drivers Andy Shevchenko
2026-02-27 11:23 ` Miclaus, Antoniu
2026-02-27 14:48 ` Andy Shevchenko [this message]
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=aaGuzkHk6kCkcyiz@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Antoniu.Miclaus@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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
all inboxes | Powered by JetHome®