From: Joshua Crofts <joshua.crofts1@gmail.com>
To: 赵文强 <berringtoni36@gmail.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Lothar Rubusch" <l.rubusch@gmail.com>,
linux@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: accel: adxl345: propagate errors when reading event configuration
Date: Sun, 11 Oct 2026 18:59:45 +0200 [thread overview]
Message-ID: <20261011185945.0673cd1e@systembl0wer> (raw)
In-Reply-To: <CAF2O-sO1YuVQWLoNT4mRN2+mzFOG-WdQ5Nt80s1k+7PP8QUtFQ@mail.gmail.com>
On Sun, 11 Oct 2026 02:15:41 -0400
赵文强 <berringtoni36@gmail.com> wrote:
> diff --git a/drivers/iio/accel/adxl345_core.c b/drivers/iio/accel/adxl345_core.c
> index 6c9080d..5983fc7 100644
> --- a/drivers/iio/accel/adxl345_core.c
> +++ b/drivers/iio/accel/adxl345_core.c
> @@ -1176,9 +1176,9 @@ static int adxl345_read_mag_config(struct
This patch is corrupted - I assume the email client you're using added
a hard break here, therefore it fails to apply :(
Additionally, you didn't use a cover letter, so patch 2 appears as a
reply to patch 1, which may break tooling.
Please use git send-email to send patches to prevent these issues.
> adxl345_state *st,
> {
> switch (dir) {
> case IIO_EV_DIR_RISING:
> - return !!adxl345_is_act_inact_en(st, type_act);
> + return adxl345_is_act_inact_en(st, type_act);
> case IIO_EV_DIR_FALLING:
> - return !!adxl345_is_act_inact_en(st, type_inact);
> + return adxl345_is_act_inact_en(st, type_inact);
> default:
> return -EINVAL;
> }
>
> base-commit: 9ee8306121495d2a25aa5d1bfd519f2748786b83
--
Kind regards,
Joshua Crofts
prev parent reply other threads:[~2026-10-11 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 6:15 赵文强
2026-10-11 6:16 ` [PATCH 2/2] iio: accel: adxl345: propagate errors when disabling activity events 赵文强
2026-10-11 16:59 ` Joshua Crofts [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=20261011185945.0673cd1e@systembl0wer \
--to=joshua.crofts1@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=berringtoni36@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=l.rubusch@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=nuno.sa@analog.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®