ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINER SUMMIT] Enforcing API deprecation
Date: Wed, 27 Aug 2025 17:31:36 +0200	[thread overview]
Message-ID: <CACMJSev0yRtCqr9YuHkN8ETyzU6_4bhuuX3ykLXNK8Z0eR1TvQ@mail.gmail.com> (raw)
In-Reply-To: <e5e72565-6421-8f1e-50d2-6deecc303faf@inria.fr>

On Wed, 27 Aug 2025 at 16:58, Julia Lawall <julia.lawall@inria.fr> wrote:
>

[snip]

> >
> > And to address your last sentence on a personal note: thing's arent
> > always so black and white - for me: I inherited the GPIO subsystem
> > with both the old and the new API already present tree-wide and am
> > just trying to improve the pre-existing situation.
>
> Is there some centralized place listing what APis need attention and
> giving some hints about what should be done?  Hints could be text or
> change examples or pointers to commits where the change has been done.
>
> julia

There's a TODO entry[1], a talk where I described the heaps of
technical debt we're dealing with[2] and lots of patches on the list
called typically something like "convert to GPIO descriptors" and
which look like this[3] or this[4] so quite different depending on
circumstances.

Bartosz

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpio/TODO#n6
[2] https://www.youtube.com/watch?v=BR41Yg69c9Y
[3] https://lore.kernel.org/all/20250808151822.536879-18-arnd@kernel.org/
[4] https://lore.kernel.org/all/20240423-gpio-leds-v1-3-799c2f6bc61c@linaro.org/

  reply	other threads:[~2025-08-27 15:31 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
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 [this message]
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=CACMJSev0yRtCqr9YuHkN8ETyzU6_4bhuuX3ykLXNK8Z0eR1TvQ@mail.gmail.com \
    --to=bartosz.golaszewski@linaro.org \
    --cc=julia.lawall@inria.fr \
    --cc=ksummit@lists.linux.dev \
    --cc=torvalds@linux-foundation.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