mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Alexandra Winter <wintera@linux.ibm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "open list:DIBS (DIRECT INTERNAL BUFFER SHARING)"
	<netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dibs: change dibs_class to a const struct
Date: Tue, 3 Mar 2026 14:23:55 +0100 (CET)	[thread overview]
Message-ID: <1787125475.222946.1772544235267@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <b4804b53-c25c-485e-8cb3-9ade70a6f625@linux.ibm.com>

Hi Alexandra,

> 
> Thank you for the patch Jori.
> Would you mind adding a link to explain the "as the driver core now allows"?
> Maybe
> Link: https://lore.kernel.org/all/2023040248-outrage-obsolete-5a9a@gregkh/
> 

Yes, see this one indeed:
https://lore.kernel.org/all/2023040244-duffel-pushpin-f738@gregkh/

> 
> For my education: How could I have noticed that class_create() call has been deprecated?
> Is that marked somewhere somehow?
>

I think this is for Greg to answer, but my guess would be that you maybe could
not have. I don't know if there is a formal deprecation procedure.

This is just cleanup work that has been laying around for a
while and some beginners like me have progressed this to gain kernel patching
experience. I see that this was already being worked on in 2023. I am now
removing the last references to class_create() in drivers so that the API
can finally be retired.

Thanks,
Jori.

  reply	other threads:[~2026-03-03 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 16:31 Jori Koolstra
2026-03-02 22:54 ` Greg Kroah-Hartman
2026-03-03 13:07   ` Alexandra Winter
2026-03-03 13:23     ` Jori Koolstra [this message]
2026-03-03 13:38       ` Alexandra Winter
2026-03-03 13:47         ` Jori Koolstra
2026-03-03 14:47           ` Alexandra Winter

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=1787125475.222946.1772544235267@kpc.webmail.kpnmail.nl \
    --to=jkoolstra@xs4all.nl \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wintera@linux.ibm.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®