All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Raka Gunarto <rakagunarto@gmail.com>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Fwd: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Date: Fri, 25 Jul 2025 14:06:31 +0200	[thread overview]
Message-ID: <2025072559-ashy-mashed-60d2@gregkh> (raw)
In-Reply-To: <CACUOwmKMAxa6gEhFRLPKPw7zu-Sb8GEtH2qgAQBT9_-LGkeZWw@mail.gmail.com>

On Fri, Jul 25, 2025 at 11:34:05AM +0100, Raka Gunarto wrote:
> Hi everyone, I'm a really new contributor and I sent off this
> RFC to LKML <https://lore.kernel.org/lkml/20250723140129.276874-1-rakagunarto@gmail.com/T/#m1372eb992552491ac37f46f27e5ad09d9efa35ad>,
> when I probably should have floated the idea
> here first. In any case, I've pasted my RFC patch below
> and I would really like any feedback / suggestions on the
> idea.

We don't take patches for code that is not actually used.  You added a
macro here that is never called, so why is it even needed?  That's a
good reason why it was ignored.

thanks,

greg k-h

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

  reply	other threads:[~2025-07-25 12:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 14:01 [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis Raka Gunarto
2025-07-23 14:03 ` [RFC PATCH 1/1] " Raka Gunarto
2025-07-25 10:34 ` Fwd: [RFC PATCH 0/1] " Raka Gunarto
2025-07-25 12:06   ` Greg KH [this message]
2025-07-25 12:18   ` Mulyadi Santosa
2025-07-25 12:42     ` Raka Gunarto
2025-07-25 13:28       ` Siddh Raman Pant
2025-07-25 13:56       ` Greg KH
2025-07-25 15:07         ` Raka Gunarto
2025-07-25 17:04           ` Tom Mitchell

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=2025072559-ashy-mashed-60d2@gregkh \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=rakagunarto@gmail.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 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.