From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Nikita Shubin <nikita.shubin@maquefel.me>,
Conor Dooley <conor@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 0/4] DONOTMERGE: ep93xx-clk from ep93xx device tree conversion
Date: Tue, 09 Apr 2024 17:09:35 +0200 [thread overview]
Message-ID: <73fd3f42c2d63467bb1b04888659e829f9e54f52.camel@gmail.com> (raw)
In-Reply-To: <42f9da044fdc11e2495f6845c061afefa796f7cf.camel@maquefel.me>
Hi Nikita,
On Tue, 2024-04-09 at 14:48 +0300, Nikita Shubin wrote:
> On Mon, 2024-04-08 at 18:03 +0100, Conor Dooley wrote:
> > On Mon, Apr 08, 2024 at 11:09:52AM +0300, Nikita Shubin via B4 Relay
> > wrote:
> > > The goal is to recieve ACKs.
> >
> > I dont see a maintainers entry in -rc1 for the drivers/soc/cirrus
> > portion. Who is gonna give you an Ack for that portion? If you
> > intended
> > maintaining that driver, should you not add a MAINTAINERS entry for
> > it?
>
> drivers/soc/cirrus got it's ACK from ep93xx MAINTAINER - Alexander
> Sverdlin.
>
> Arnd, Alexander - should we add it now ?
seems that we have couple of things to fix:
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#51:
new file mode 100644
WARNING: please write a help paragraph that fully describes the config symbol
#60: FILE: drivers/soc/cirrus/Kconfig:5:
+config EP93XX_SOC
+ bool "Cirrus EP93xx chips SoC"
+ select SOC_BUS
+ select AUXILIARY_BUS
+ default y if !EP93XX_SOC_COMMON
+ help
+ Support SoC for Cirrus EP93xx chips.
+
total: 0 errors, 2 warnings, 269 lines checked
--
Alexander Sverdlin.
next prev parent reply other threads:[~2024-04-09 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 8:09 [PATCH 0/4] DONOTMERGE: ep93xx-clk from ep93xx device tree conversion Nikita Shubin via B4 Relay
2024-04-08 8:09 ` [PATCH 1/4] ARM: ep93xx: add regmap aux_dev Nikita Shubin via B4 Relay
2024-04-11 9:32 ` Stephen Boyd
2024-04-08 8:09 ` [PATCH 2/4] clk: ep93xx: add DT support for Cirrus EP93xx Nikita Shubin via B4 Relay
2024-04-11 9:32 ` Stephen Boyd
2024-04-14 9:35 ` Nikita Shubin
2024-04-08 8:09 ` [PATCH 3/4] dt-bindings: soc: Add " Nikita Shubin via B4 Relay
2024-04-11 9:21 ` Stephen Boyd
2024-04-08 8:09 ` [PATCH 4/4] soc: Add SoC driver for Cirrus ep93xx Nikita Shubin via B4 Relay
2024-04-11 9:26 ` Stephen Boyd
2024-04-08 17:03 ` [PATCH 0/4] DONOTMERGE: ep93xx-clk from ep93xx device tree conversion Conor Dooley
2024-04-09 11:48 ` Nikita Shubin
2024-04-09 15:09 ` Alexander Sverdlin [this message]
2024-04-09 17:32 ` 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=73fd3f42c2d63467bb1b04888659e829f9e54f52.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nikita.shubin@maquefel.me \
--cc=robh@kernel.org \
--cc=sboyd@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 read-only IMAP folder(s) and NNTP newsgroup(s).