From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Lee Jones <lee.jones@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Dmitry Osipenko <digetx@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>
Cc: Mark Brown <broonie@kernel.org>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v1 0/3] Remove TPS80031 driver
Date: Sat, 23 Oct 2021 20:58:03 +0100 [thread overview]
Message-ID: <163501903136.919198.2215583761573321430.b4-ty@kernel.org> (raw)
In-Reply-To: <20211021192258.21968-1-digetx@gmail.com>
On Thu, 21 Oct 2021 22:22:55 +0300, Dmitry Osipenko wrote:
> TPS80031 driver was upstreamed back in 2013 and never got a user. I noticed
> that driver is abandoned while was about to write a patch to switch it to a
> new power-off API (that I'm working on). Driver requires platform data that
> nobody provides. Instead of changing the dead code, let's remove it.
>
> Dmitry Osipenko (3):
> rtc: tps80031: Remove driver
> regulator: tps80031: Remove driver
> mfd: tps80031: Remove driver
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[2/3] regulator: tps80031: Remove driver
commit: d7477e646291b2dcdd5521cf926cd390ddd6a7c1
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2021-10-23 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 19:22 Dmitry Osipenko
2021-10-21 19:22 ` [PATCH v1 1/3] rtc: tps80031: Remove driver Dmitry Osipenko
2021-10-23 21:55 ` (subset) " Alexandre Belloni
2021-10-21 19:22 ` [PATCH v1 2/3] regulator: " Dmitry Osipenko
2021-10-21 19:22 ` [PATCH v1 3/3] mfd: " Dmitry Osipenko
2021-10-22 8:05 ` Lee Jones
2021-10-22 8:20 ` Dmitry Osipenko
2021-10-22 8:46 ` Wolfram Sang
2021-10-22 8:50 ` Dmitry Osipenko
2021-10-22 9:54 ` Lee Jones
2021-10-22 10:02 ` Lee Jones
2021-10-23 19:58 ` Mark Brown [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=163501903136.919198.2215583761573321430.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=digetx@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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
all inboxes | Powered by JetHome®