From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Petre Rodan" <petre.rodan@subdimension.ro>,
"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>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH v6 2/2] iio: pressure: abp2030pa: remove error message
Date: Wed, 14 Jan 2026 08:53:02 +0000 [thread overview]
Message-ID: <20260114085302.6650777d@jic23-huawei> (raw)
In-Reply-To: <CAHp75VeUkNEHeF5ey08AU+drZKunL5PzoSJ=0JPXzc0Z2Um3ng@mail.gmail.com>
On Wed, 14 Jan 2026 09:55:22 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Wed, Jan 14, 2026 at 9:52 AM Petre Rodan <petre.rodan@subdimension.ro> wrote:
> >
> > Do not print redundant error message if devm_request_irq() fails.
>
> the duplicate
I went with "a duplicate" as it seemed to read better to my ear.
Tweaked and applied.
Thanks,
Jonathan
>
> (It's not redundant, it's duplicate because that API prints something
> very similar.)
>
> P.S. Do not send a new version for this, I hope Jonathan can tweak
> this small detail whilst applying.
>
prev parent reply other threads:[~2026-01-14 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 7:51 [PATCH v6 0/2] iio: pressure: abp2030pa: cleanup Petre Rodan
2026-01-14 7:51 ` [PATCH v6 1/2] iio: pressure: abp2030pa: fix typo in Kconfig description Petre Rodan
2026-01-14 8:51 ` Jonathan Cameron
2026-01-14 7:51 ` [PATCH v6 2/2] iio: pressure: abp2030pa: remove error message Petre Rodan
2026-01-14 7:55 ` Andy Shevchenko
2026-01-14 8:53 ` Jonathan Cameron [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=20260114085302.6650777d@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=petre.rodan@subdimension.ro \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox