From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Binbin Zhou <zhoubinbin@loongson.cn>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: Chong Qiao <qiaochong@loongson.cn>, Lee Jones <lee@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Corey Minyard <corey@minyard.net>
Subject: [PATCH v2 0/2] mfd: ls2kbmc: A fix and a refactoring
Date: Thu, 13 Nov 2025 17:22:49 +0100 [thread overview]
Message-ID: <20251113162713.3143777-1-andriy.shevchenko@linux.intel.com> (raw)
Just an ad-hoc fix and refactoring as I have noticed the problematic fix,
which is commit 4af66c2bcab0 ("mfd: ls2kbmc: check for devm_mfd_add_devices()
failure") in the Linux Next.
The best, actually to get that change simply being dropped or reverted,
as this whole series was induced by that (wrong) attempt to fix things.
Changelog v2:
- fixed spelling (Lee)
- rebased on top of for-mfd-next (Lee)
- collected tags (Binbin)
v1: <20251030113735.3741913-1-andriy.shevchenko@linux.intel.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Corey Minyard <corey@minyard.net>
Andy Shevchenko (2):
mfd: ls2kbmc: Fully convert to use managed resources
mfd: ls2kbmc: Use PCI API instead of direct accesses
drivers/mfd/ls2k-bmc-core.c | 32 +++++++++-----------------------
1 file changed, 9 insertions(+), 23 deletions(-)
--
2.50.1
next reply other threads:[~2025-11-13 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 16:22 Andy Shevchenko [this message]
2025-11-13 16:22 ` [PATCH v2 1/2] mfd: ls2kbmc: Fully convert to use managed resources Andy Shevchenko
2025-11-19 16:47 ` Lee Jones
2025-11-19 16:59 ` Andy Shevchenko
2025-11-20 8:54 ` Lee Jones
2025-11-20 9:11 ` Andy Shevchenko
2025-11-20 13:39 ` Lee Jones
2025-11-20 13:48 ` Andy Shevchenko
2025-12-14 14:57 ` (subset) " Lee Jones
2025-11-13 16:22 ` [PATCH v2 2/2] mfd: ls2kbmc: Use PCI API instead of direct accesses Andy Shevchenko
2025-12-14 14:57 ` [PATCH v2 0/2] mfd: ls2kbmc: A fix and a refactoring Lee Jones
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=20251113162713.3143777-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=corey@minyard.net \
--cc=dan.carpenter@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiaochong@loongson.cn \
--cc=zhoubinbin@loongson.cn \
/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