From: Emil Renner Berthing <emil.renner.berthing@canonical.com>
To: Hal Feng <hal.feng@starfivetech.com>
Cc: Conor Dooley <conor@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] MAINTAINERS: Add Hal as a maintainer of SFCTEMP HWMON DRIVER
Date: Thu, 10 Aug 2023 13:35:16 +0200 [thread overview]
Message-ID: <CAJM55Z_p4rFXVOUvXKRPH1r7KSXkVbSNtZAGA5Dyzw7TNfuLtA@mail.gmail.com> (raw)
In-Reply-To: <e63baeee-134c-db4f-f350-b3526a0ae571@starfivetech.com>
On Fri, 21 Jul 2023 at 05:24, Hal Feng <hal.feng@starfivetech.com> wrote:
> On Tue, 18 Jul 2023 15:20:15 +0100, Conor Dooley wrote:
> > On Tue, Jul 18, 2023 at 11:49:37AM +0800, Hal Feng wrote:
> >> As he is the submitter of this driver, add his mail so he can
> >> maintain the driver and easily reply in the mailing list.
> >>
> >> Signed-off-by: Hal Feng <hal.feng@starfivetech.com>
> >> ---
> >> MAINTAINERS | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index aee340630eca..5056079ade77 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -19256,6 +19256,7 @@ F: drivers/net/ethernet/sfc/
> >>
> >> SFCTEMP HWMON DRIVER
> >> M: Emil Renner Berthing <kernel@esmil.dk>
> >> +M: Hal Feng <hal.feng@starfivetech.com>
> >> L: linux-hwmon@vger.kernel.org
> >> S: Maintained
> >> F: Documentation/devicetree/bindings/hwmon/starfive,jh71x0-temp.yaml
> >
> > Whatever about the other patches in this series, this one certainly
> > needs an Ack from Emil.
>
> Hi @Emil,
>
> Would you mind adding me as one of the maintainers of this driver?
> Within StarFive, I was appointed to maintain this driver.
Hey, sorry about the late reply. That's absolutely fine by me.
/Emil
> Best regards,
> Hal
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-10 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 3:49 [PATCH v1 0/3] riscv: dts: starfive: jh71x0: Add temperature sensor nodes and thermal-zones Hal Feng
2023-07-18 3:49 ` [PATCH v1 1/3] riscv: dts: starfive: jh7100: Add temperature sensor node " Hal Feng
2023-07-18 3:49 ` [PATCH v1 2/3] riscv: dts: starfive: jh7110: " Hal Feng
2023-07-18 3:49 ` [PATCH v1 3/3] MAINTAINERS: Add Hal as a maintainer of SFCTEMP HWMON DRIVER Hal Feng
2023-07-18 14:20 ` Conor Dooley
2023-07-21 3:24 ` Hal Feng
2023-08-10 11:35 ` Emil Renner Berthing [this message]
2023-08-10 11:36 ` Emil Renner Berthing
2023-07-20 16:29 ` (subset) [PATCH v1 0/3] riscv: dts: starfive: jh71x0: Add temperature sensor nodes and thermal-zones Conor Dooley
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=CAJM55Z_p4rFXVOUvXKRPH1r7KSXkVbSNtZAGA5Dyzw7TNfuLtA@mail.gmail.com \
--to=emil.renner.berthing@canonical.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).