Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Richard <richard_siegfried@systemli.org>
To: kernelnewbies@kernelnewbies.org
Subject: ktypes vs. devices classes (struct class)
Date: Sat, 30 Sep 2023 02:12:41 +0200	[thread overview]
Message-ID: <9644b2e3-acaf-c26b-0ec2-9a6c9cb23977@systemli.org> (raw)

Hi all,

Why do we have ktypes (struct kobj_type) AND device classes (struct class)?

Don't they serve the same purpose (more or less) and it would be 
simpler, clearer and more KISS to only have one? Is this a historically 
grown thing or by design?

Thanks,
-- Richard

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2023-09-30  0:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30  0:12 Richard [this message]
2023-09-30  6:30 ` ktypes vs. devices classes (struct class) Greg KH
2023-09-30 18:17   ` Richard
2023-10-01  9:50     ` Greg KH
2023-10-01 10:28       ` Greg KH
2023-10-01 21:22         ` Richard
2023-10-01 21:15       ` Richard
2023-10-02  9:00         ` Greg KH

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=9644b2e3-acaf-c26b-0ec2-9a6c9cb23977@systemli.org \
    --to=richard_siegfried@systemli.org \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).