From: Mark Brown <broonie@kernel.org>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: Axel Lin <axel.lin@ingics.com>,
Support Opensource <Support.Opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] regulator: da9055: Convert to regulator core's simplified DT parsing code
Date: Mon, 18 Mar 2019 14:25:58 +0000 [thread overview]
Message-ID: <20190318142558.GF6221@sirena.org.uk> (raw)
In-Reply-To: <VI1PR10MB2352F3E21A79E28D0F0EDA85FE470@VI1PR10MB2352.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Mon, Mar 18, 2019 at 01:56:21PM +0000, Steve Twiss wrote:
> But it does seem that around 97% of this driver has not has not changed since
> 2014, so we are happy here at Dialog to remove our support from this DA9055
> device.
> Is there a Linux device driver retirement plan for obsoleted products? :)
Well, we can delete stuff but personally I don't see a big concern with
leaving things sitting there so long as they're not getting in anyone's
way - it's more effort to figure out if there's any users (like with
this if there's people with old boards somewhere even if the product
isn't being sold yet) than it is just to leave things sitting there. If
you don't want to do any support on it that's fine though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-03-18 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:47 [PATCH 1/2] regulator: da9052: " Axel Lin
2019-03-12 15:47 ` [PATCH 2/2] regulator: da9055: " Axel Lin
2019-03-18 13:56 ` Steve Twiss
2019-03-18 14:25 ` 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=20190318142558.GF6221@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Support.Opensource@diasemi.com \
--cc=axel.lin@ingics.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stwiss.opensource@diasemi.com \
/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®