From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINER SUMMIT] Enforcing API deprecation
Date: Wed, 27 Aug 2025 09:57:44 -0700 [thread overview]
Message-ID: <CAHk-=whkAe8f4=ttQmZhtoKvGtCLhEA-oHwUEvQFftYAwfVwCA@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKqO2Qg6VnRaotQdfrfoo78Y8AA1AKQBrD_XVSEK2BMgA@mail.gmail.com>
On Wed, 27 Aug 2025 at 09:42, Rob Herring <robherring2@gmail.com> wrote:
>
> I have a similar situation with DT APIs. It's a bit more nuanced than
> the GPIO case. There's old APIs which are "don't add new users" or
> "think twice before you add a new user". We may never get rid of the
> APIs because a) no one wants to fix PPC and Sparc and b) there's
> sometimes a need for these lower level functions. It's similar to
> using devm_ APIs vs. the non devm_ variants.
Having parallel APIs for different use cases is perfectly fine.
Normal, even, and not something that we should worry about or even
strive to avoid.
The devm_xyz() vs just plain xyz() is a good example of that. They are
parallel for good reasons, and they will remain forever.
All I'm saying is that people who do new API's should either just
accept that, or just convert between the two. None of this "deprecate"
garbage. None of this "blame other developers because they use the old
interface".
That's the basic tenet here: if you are too lazy to convert all users,
you also do not have the moral right to complain about - or expect -
others not doing the work you didn't do for you.
Linus
next prev parent reply other threads:[~2025-08-27 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 19:57 Bartosz Golaszewski
2025-08-26 20:12 ` Linus Torvalds
2025-08-26 20:28 ` Jiri Kosina
2025-08-26 22:44 ` Linus Torvalds
2025-08-26 23:25 ` Al Viro
2025-08-27 15:07 ` Bartosz Golaszewski
2025-08-27 16:42 ` Rob Herring
2025-08-27 16:57 ` Linus Torvalds [this message]
2025-08-28 15:11 ` Bartosz Golaszewski
2025-09-03 13:19 ` Eric W. Biederman
2025-08-27 14:47 ` Bartosz Golaszewski
2025-08-27 14:58 ` Julia Lawall
2025-08-27 15:31 ` Bartosz Golaszewski
2025-08-29 9:00 ` Krzysztof Kozlowski
2025-08-26 20:24 ` Johannes Berg
2025-08-26 21:02 ` Laurent Pinchart
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='CAHk-=whkAe8f4=ttQmZhtoKvGtCLhEA-oHwUEvQFftYAwfVwCA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=robherring2@gmail.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