From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Ethan Tidmore" <ethantidmore06@gmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Multiple bug fixes
Date: Mon, 23 Feb 2026 20:42:23 -0600 [thread overview]
Message-ID: <DGMUGO8B7SZ5.15TPOD74KU0Q3@gmail.com> (raw)
In-Reply-To: <20260224023511.274038-1-ethantidmore06@gmail.com>
On Mon Feb 23, 2026 at 8:35 PM CST, Ethan Tidmore wrote:
Just realized I didn't put a changelog, the only actual changes is the
implementation of devm_ to manual cleanup with Patch 2 [1]. The rest are
new patches.
[1] https://lore.kernel.org/all/20260220200522.19967-1-ethantidmore06@gmail.com/
Thanks,
ET
next prev parent reply other threads:[~2026-02-24 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 2:35 [PATCH v2 0/4] Multiple bug fixes Ethan Tidmore
2026-02-24 2:35 ` [PATCH v2 1/4] iio: gyro: mpu3050: Fix incorrect free_irq() variable Ethan Tidmore
2026-02-24 9:55 ` Linus Walleij
2026-02-24 10:02 ` Andy Shevchenko
2026-02-24 2:35 ` [PATCH v2 2/4] iio: gyro: mpu3050: Fix irq resource leak Ethan Tidmore
2026-02-24 9:56 ` Linus Walleij
2026-02-24 10:03 ` Andy Shevchenko
2026-02-24 2:35 ` [PATCH v2 3/4] iio: gyro: mpu3050: Move iio_device_register() to correct location Ethan Tidmore
2026-02-24 9:56 ` Linus Walleij
2026-02-24 10:05 ` Andy Shevchenko
2026-02-24 2:35 ` [PATCH v2 4/4] iio: gyro: mpu3050: Fix out-of-sequence free_irq() Ethan Tidmore
2026-02-24 9:57 ` Linus Walleij
2026-02-24 10:06 ` Andy Shevchenko
2026-02-24 2:42 ` Ethan Tidmore [this message]
2026-02-24 10:08 ` [PATCH v2 0/4] Multiple bug fixes 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=DGMUGO8B7SZ5.15TPOD74KU0Q3@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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