All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Iskren Chernev <iskren.chernev@gmail.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Matheus Castello <matheus@castello.eng.br>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@puri.sm
Subject: Re: [PATCH 1/2] MAINTAINERS: power: supply: max17042: add entry with reviewers
Date: Tue, 12 Oct 2021 17:40:36 +0200	[thread overview]
Message-ID: <20211012154036.hyaabb6okzcgdlyw@earth.universe> (raw)
In-Reply-To: <4803957.ieAp1BVO2D@pliszka>

[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]

Hi,

On Sat, Sep 25, 2021 at 02:31:44PM +0200, Sebastian Krzyszkowiak wrote:
> On piątek, 24 września 2021 13:56:18 CEST Krzysztof Kozlowski wrote:
> > The Maxim max17042 fuel gauge driver supports several devices used on
> > multiple different boards - both devicetree and ACPI based.  The driver
> > is incomplete and has few known issues.  Fixing these might break other
> > platforms so mention recent contributors who can provide feedback.  This
> > way most of interested parties might help reviewing the patches.
> > 
> > Cc: Hans de Goede <hdegoede@redhat.com>
> > Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> > Cc: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> > ---
> >  MAINTAINERS | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 329d3a0a9fdb..da9d5383af04 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -11429,6 +11429,16 @@ S:	Maintained
> >  F:	Documentation/devicetree/bindings/iio/proximity/
> maxbotix,mb1232.yaml
> >  F:	drivers/iio/proximity/mb1232.c
> > 
> > +MAXIM MAX17042 FAMILY FUEL GAUGE DRIVERS
> > +R:	Hans de Goede <hdegoede@redhat.com>
> > +R:	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> > +R:	Marek Szyprowski <m.szyprowski@samsung.com>
> > +R:	Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
> 
> I think it may be worth adding:
> 
> +R:	Purism Kernel Team <kernel@puri.sm>
> 
> In any case:
> 
> Reviewed-by: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>

Thanks, I queued both patches with the Purism Kernel Team added for
MAX17042.

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-10-12 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 11:56 [PATCH 1/2] MAINTAINERS: power: supply: max17042: add entry with reviewers Krzysztof Kozlowski
2021-09-24 11:56 ` [PATCH 2/2] MAINTAINERS: power: supply: max17040: " Krzysztof Kozlowski
2021-09-24 13:06 ` [PATCH 1/2] MAINTAINERS: power: supply: max17042: " Hans de Goede
2021-09-25 12:31 ` Sebastian Krzyszkowiak
2021-10-12 15:40   ` Sebastian Reichel [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=20211012154036.hyaabb6okzcgdlyw@earth.universe \
    --to=sebastian.reichel@collabora.com \
    --cc=hdegoede@redhat.com \
    --cc=iskren.chernev@gmail.com \
    --cc=kernel@puri.sm \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=matheus@castello.eng.br \
    --cc=sebastian.krzyszkowiak@puri.sm \
    /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.