From: Xu Yilun <yilun.xu@intel.com>
To: lee.jones@linaro.org, linux-kernel@vger.kernel.org
Cc: trix@redhat.com, yilun.xu@intel.com,
matthew.gerlach@linux.intel.com, russell.h.weight@intel.com,
lgoncalv@redhat.com, hao.wu@intel.com
Subject: [PATCH v4 0/4] Some improvement for Intel MAX 10 MFD drivers
Date: Wed, 10 Mar 2021 23:55:44 +0800 [thread overview]
Message-ID: <1615391748-1733-1-git-send-email-yilun.xu@intel.com> (raw)
This patchset is some improvements for intel-m10-bmc and its subdevs.
Main changes from v1:
- Add a patch (#2) to simplify the definition of the legacy version reg.
- Add a patch (#4), add entry in MAINTAINERS for intel-m10-bmc mfd driver
and the subdev drivers.
Main changes from v2:
- Add Tom Rix as the reviewer for intel-m10-bmc mfd driver and the subdev
drivers.
- Rebased to 5.12-rc1
Main changes from v3:
- Improve the comments for valid version check.
Matthew Gerlach (1):
mfd: intel-m10-bmc: Add access table configuration to the regmap
Xu Yilun (3):
mfd: intel-m10-bmc: Fix the register access range
mfd: intel-m10-bmc: Simplify the legacy version reg definition
MAINTAINERS: Add entry for Intel MAX 10 mfd driver
MAINTAINERS | 10 ++++++++++
drivers/mfd/intel-m10-bmc.c | 30 ++++++++++++++++++++----------
include/linux/mfd/intel-m10-bmc.h | 7 +++++--
3 files changed, 35 insertions(+), 12 deletions(-)
--
2.7.4
next reply other threads:[~2021-03-10 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 15:55 Xu Yilun [this message]
2021-03-10 15:55 ` [PATCH v4 1/4] mfd: intel-m10-bmc: Fix the register access range Xu Yilun
2021-03-10 15:55 ` [PATCH v4 2/4] mfd: intel-m10-bmc: Simplify the legacy version reg definition Xu Yilun
2021-03-10 15:55 ` [PATCH v4 3/4] mfd: intel-m10-bmc: Add access table configuration to the regmap Xu Yilun
2021-03-10 15:55 ` [PATCH v4 4/4] MAINTAINERS: Add entry for Intel MAX 10 mfd driver Xu Yilun
2021-03-10 16:35 ` [PATCH v4 0/4] Some improvement for Intel MAX 10 MFD drivers 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=1615391748-1733-1-git-send-email-yilun.xu@intel.com \
--to=yilun.xu@intel.com \
--cc=hao.wu@intel.com \
--cc=lee.jones@linaro.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.