All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leam Hall <leamhall@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Typecasting a void pointer to unsigned long in zsmalloc.c
Date: Mon, 27 Jan 2025 07:48:38 -0600	[thread overview]
Message-ID: <93cf1346-b9e0-3f0f-739a-ed7d4176b800@gmail.com> (raw)
In-Reply-To: <CACYkWJ65OnWBOAohs3ovx+z6sbCsTvX2qfA-XGHWHPmyESEgOQ@mail.gmail.com>

On 1/27/25 04:39, Sotir Danailov wrote:
> On Mon, Jan 27, 2025 at 12:43 AM Leam Hall <leamhall@gmail.com> wrote:
>> I'd think pointing to good documents is better than replicating them and risk staleness, isn't it?
> 
> Yes, but then the issue becomes, what if the documentation you're
> referencing moves or is removed. People would lose the information
> completely. I think it's good to point to it as a "source", but still
> have a basic description.
> The LP32/LP64 data models seem like one of those things which
> shouldn't change anytime soon for the kernel anyway.
> 
> I would like to gather info regarding uintptr_t and other similar
> types as well. Why they aren't used and have it all compiled into one
> place.


My thinking is that a single authoritative source reduces time and change based risk. You really dug into this and found the information, the facts. Those facts can't actually be removed because they are part of the kernel code itself. Well, they can be removed but then they are no longer relevant facts. KernelNewbies is the gentle introduction to working on Linux, but much of its information is dated. Kernel 2.x is referenced often, and we're currently up to 6.x! That's one of the things I want to fix.

If you want my opinion, I'll offer it. The research you did was great, and useful for kernel programmers. I feel it is a more advanced topic, something a newbie wouldn't have a significant mental frame of reference for. Here are the sites that seem most relevant:


kernel.org
  - authoritative source of facts
  - encourage those who have access (which is not me) and responsibility to improve the documentation of those facts

tldp.org
  - In-depth information on Linux facts
  - - Sadly, it seems to be aging as the latest Guides update is almost ten years old

kernelnewbies.org
  - Help newbies find and use facts


Would you consider writing up a guide for either tldp.org or kernel.org?

Leam


Linux Software Engineer   (reuel.net/career)
Scribe: The Domici War    (domiciwar.net)
Coding Ne'er-do-well      (github.com/LeamHall)

Between "can" and "can't" is a gap of "I don't know", a place of discovery. For the passionate, much of "can't" falls into "yet". -- lh

Practice allows options and foresight. -- lh
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2025-01-27 13:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 15:52 Typecasting a void pointer to unsigned long in zsmalloc.c Sotir Danailov
2025-01-23 15:59 ` Greg KH
2025-01-23 16:27   ` Sotir Danailov
2025-01-23 17:00     ` Greg KH
2025-01-23 17:05       ` Sotir Danailov
2025-01-23 17:40         ` Leam Hall
2025-01-23 18:30           ` Sotir Danailov
2025-01-23 19:54             ` Leam Hall
2025-01-23 20:48               ` Sotir Danailov
2025-01-23 21:09                 ` Costa Shulyupin
2025-01-24  5:13                   ` Greg KH
2025-01-24 21:45                     ` Sotir Danailov
2025-01-26 23:29                       ` Leam Hall
2025-01-27 10:39                         ` Sotir Danailov
2025-01-27 13:48                           ` Leam Hall [this message]
2025-01-28  8:45                             ` Sotir Danailov
2025-01-28  8:58                               ` Costa Shulyupin
2025-01-28  9:14                                 ` Sotir Danailov
2025-01-28  9:24                           ` Sotir Danailov
2025-01-28 10:23                             ` Leam Hall
2025-01-23 18:44     ` jim.cromie
     [not found] <mailman.1.1737651601.26911.kernelnewbies@kernelnewbies.org>
2025-01-23 17:58 ` Alex Hogen
2025-01-23 18:23   ` 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=93cf1346-b9e0-3f0f-739a-ed7d4176b800@gmail.com \
    --to=leamhall@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.