From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.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>,
Bartosz Golaszewski <brgl@bgdev.pl>,
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: [RESEND PATCH 0/4] Drop ROHM BD70528 support
Date: Sun, 31 Oct 2021 15:06:05 +0200 [thread overview]
Message-ID: <CAHp75Vf12Lx=demULkNhgP=YpnfdH15Y9T5C7PUA4uo=0J15ZQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1635412162.git.matti.vaittinen@fi.rohmeurope.com>
On Thu, Oct 28, 2021 at 12:18 PM Matti Vaittinen
<matti.vaittinen@fi.rohmeurope.com> wrote:
>
> Drop ROHM BD70528 support
I am always for the code removal, but the Q here is do you think there
won't be similar chips that may utilize the code and avoid duplication
in the future?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-10-31 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 9:18 [RESEND PATCH 0/4] Drop ROHM BD70528 support Matti Vaittinen
2021-10-28 9:18 ` [RESEND PATCH 1/4] dt-bindings: mfd: regulator: Drop " Matti Vaittinen
2021-11-08 17:55 ` Rob Herring
2021-10-28 9:18 ` [RESEND PATCH 2/4] gpio: bd70528 " Matti Vaittinen
2021-10-28 9:19 ` [RESEND PATCH 3/4] mfd: bd70528: " Matti Vaittinen
2021-10-28 9:19 ` [RESEND PATCH 4/4] MAINTAINERS: bd70528: Drop ROHM BD70528 drivers Matti Vaittinen
2021-10-31 13:06 ` Andy Shevchenko [this message]
2021-11-01 6:18 ` [RESEND PATCH 0/4] Drop ROHM BD70528 support Vaittinen, Matti
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='CAHp75Vf12Lx=demULkNhgP=YpnfdH15Y9T5C7PUA4uo=0J15ZQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--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).