From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-power <linux-power@fi.rohmeurope.com>
Subject: Re: [PATCH RESEND 0/4] Drop ROHM BD70528 support
Date: Tue, 16 Nov 2021 20:33:26 +0100 [thread overview]
Message-ID: <CAMRc=Mc-+ZR1PR9p=cXkfMWdKn1d1VCxmhBknSzNaDjepfpV-g@mail.gmail.com> (raw)
In-Reply-To: <50c260a1-c6d0-1a0b-45da-ab1a2d1379c3@gmail.com>
On Tue, Nov 16, 2021 at 7:41 PM Matti Vaittinen
<mazziesaccount@gmail.com> wrote:
>
> On 11/16/21 18:10, Andy Shevchenko wrote:
> > On Tue, Nov 16, 2021 at 2:52 PM Matti Vaittinen
> > <matti.vaittinen@fi.rohmeurope.com> wrote:
> >>
> >> Drop ROHM BD70528 support
> >>
> >> Unfortunately there has not been a big demand for ROHM BD70528
> >> IC. The few users I know control PMIC from separate M4-core,
> >> which is not running Linux. I am not aware of any users of this
> >> Linux driver.
> >>
> >> While I did really like this IC and writing the drivers for it,
> >> seems like these drivers are becoming useless burden. So, I see
> >> no point in maintaining them. Let's just drop the drivers if
> >> there is no objections to this series. :(
> >>
> >> The regulator, WDG and power-supply drivers were already dropped.
> >>
> >> The RTC and clk drivers remain in use by few other ROHM IC drivers.
> >> Nevertheless, they are already converted to not depend the BD70528
> >> defines during previous cycle.
> >>
> >> This series cleans the remaining pieces, GPIO, MFD, dt-bindings and
> >> MAINTAINER entries. The GPIO code uses defines from MFD - but the GPIO
> >> part is also depending on MFD KConfig entry - so there should be no
> >> breakages even if the patches were applied to respective subsystem trees
> >> and were not carried via single tree.
> >
> > FWIW, no objections from me.
>
> Thanks Andy!
>
> I see acks from Andu, Bartosz, Lee and Rob. It'd be nice to see ack from
> Linus W too - but other than that - I guess this is good to go. Any
> preferences regarding the tree(s) that could carry the patches? All via
> MFD or each patch merged to the subsystem it fits the best?
>
> Best Regards
> Matti Vaittinen
Normally Lee takes MFD patches together with those touching relevant subsystems.
Bart
next prev parent reply other threads:[~2021-11-16 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 12:51 [PATCH RESEND 0/4] Drop ROHM BD70528 support Matti Vaittinen
2021-11-16 12:53 ` [PATCH RESEND 1/4] dt-bindings: mfd: regulator: Drop " Matti Vaittinen
2021-11-29 12:02 ` Lee Jones
2021-11-16 12:54 ` [PATCH RESEND 2/4] gpio: bd70528 " Matti Vaittinen
2021-11-29 12:02 ` Lee Jones
2021-11-16 12:54 ` [PATCH RESEND 3/4] mfd: bd70528: " Matti Vaittinen
2021-11-29 12:01 ` Lee Jones
2021-11-16 12:55 ` [PATCH RESEND 4/4] MAINTAINERS: bd70528: Drop ROHM BD70528 drivers Matti Vaittinen
2021-11-29 12:03 ` Lee Jones
2021-11-16 16:10 ` [PATCH RESEND 0/4] Drop ROHM BD70528 support Andy Shevchenko
2021-11-16 18:41 ` Matti Vaittinen
2021-11-16 19:33 ` Bartosz Golaszewski [this message]
2021-11-18 8:55 ` Lee Jones
2021-11-16 22:52 ` Linus Walleij
2021-11-29 12:06 ` [GIT PULL] Immutable branch between MFD, GPIO and Regulator due for the v5.17 merge window 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='CAMRc=Mc-+ZR1PR9p=cXkfMWdKn1d1VCxmhBknSzNaDjepfpV-g@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-power@fi.rohmeurope.com \
--cc=lukas.bulwahn@gmail.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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).