From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: Jori Koolstra <jkoolstra@xs4all.nl>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] pps: change pps_class to a const struct
Date: Mon, 2 Mar 2026 14:09:46 -0500 [thread overview]
Message-ID: <2026030231-captivate-financial-35d3@gregkh> (raw)
In-Reply-To: <e64eef6d-df91-4428-bdc6-20347eeaac2d@enneenne.com>
On Mon, Mar 02, 2026 at 06:03:40PM +0100, Rodolfo Giometti wrote:
> On 3/2/26 17:43, Greg Kroah-Hartman wrote:
> > On Mon, Mar 02, 2026 at 04:24:40PM +0100, Rodolfo Giometti wrote:
> > > On 3/2/26 16:11, Jori Koolstra wrote:
> > > > The class_create() call has been deprecated in favor of class_register()
> > > > as the driver core now allows for a struct class to be in read-only
> > > > memory. Change pps_class to be a const struct class and drop the
> > > > class_create() call.
> > > >
> > > > Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > Signed-off-by: Jori Koolstra <jkoolstra@xs4all.nl>
> > >
> > > Acked-by: Rodolfo Giometti <giometti@enneenne.com>
> >
> > Wait, want me to pick these up through my tree? no objection if you
> > want me to, just need to know.
>
> Andrew usually adds the PPS patches, but we can use your tree too. :)
Which ever you want is easiest for me, your call.
next prev parent reply other threads:[~2026-03-02 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 15:11 [PATCH] pps: change pps_class to a const struct Jori Koolstra
2026-03-02 15:24 ` Rodolfo Giometti
2026-03-02 16:43 ` Greg Kroah-Hartman
2026-03-02 17:03 ` Rodolfo Giometti
2026-03-02 19:09 ` Greg Kroah-Hartman [this message]
2026-04-01 17:01 ` Jori Koolstra
2026-03-02 16:42 ` Greg Kroah-Hartman
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=2026030231-captivate-financial-35d3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=giometti@enneenne.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-kernel@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