public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Xu Yilun <yilun.xu@intel.com>
Cc: linux-kernel@vger.kernel.org, trix@redhat.com,
	matthew.gerlach@linux.intel.com, russell.h.weight@intel.com,
	lgoncalv@redhat.com, hao.wu@intel.com
Subject: Re: [PATCH v3 0/4] Some improvement for Intel MAX 10 MFD drivers
Date: Mon, 8 Mar 2021 09:01:24 +0000	[thread overview]
Message-ID: <20210308090124.GA4931@dell> (raw)
In-Reply-To: <20210308020454.GA32151@yilunxu-OptiPlex-7050>

On Mon, 08 Mar 2021, Xu Yilun wrote:

> Hi Lee:
> 
> Could you please help on review this patchset? They are some
> improvements for intel-m10-bmc MFD driver.

Please don't send contentless pings 1 week after submitting a set.

Also please refrain from top-posting.

This patch is on my TO-REVIEW list.

Unfortunately, since I work in reverse chronological order, you just
pushed the set to the back of the list.

If after a suitable period, usually around 2 weeks, you think your
submission has been missed, please submit a [RESEND] instead.

> On Mon, Mar 01, 2021 at 01:59:41PM +0800, Xu Yilun wrote:
> > 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
> > 
> > 
> > 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       | 25 ++++++++++++++++++-------
> >  include/linux/mfd/intel-m10-bmc.h |  7 +++++--
> >  3 files changed, 33 insertions(+), 9 deletions(-)
> > 

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2021-03-08  9:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  5:59 [PATCH v3 0/4] Some improvement for Intel MAX 10 MFD drivers Xu Yilun
2021-03-01  5:59 ` [PATCH v3 1/4] mfd: intel-m10-bmc: Fix the register access range Xu Yilun
2021-03-10  9:16   ` Lee Jones
2021-03-01  5:59 ` [PATCH v3 2/4] mfd: intel-m10-bmc: Simplify the legacy version reg definition Xu Yilun
2021-03-10  9:16   ` Lee Jones
2021-03-10 15:53     ` Xu Yilun
2021-03-01  5:59 ` [PATCH v3 3/4] mfd: intel-m10-bmc: Add access table configuration to the regmap Xu Yilun
2021-03-10  9:18   ` Lee Jones
2021-03-01  5:59 ` [PATCH v3 4/4] MAINTAINERS: Add entry for Intel MAX 10 mfd driver Xu Yilun
2021-03-10  9:19   ` Lee Jones
2021-03-08  2:04 ` [PATCH v3 0/4] Some improvement for Intel MAX 10 MFD drivers Xu Yilun
2021-03-08  9:01   ` Lee Jones [this message]
2021-03-08 14:42     ` Xu Yilun
2021-03-08 15:31       ` 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=20210308090124.GA4931@dell \
    --to=lee.jones@linaro.org \
    --cc=hao.wu@intel.com \
    --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 \
    --cc=yilun.xu@intel.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