mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Weijie Yuan <kernel@wyuan.org>, Dongliang Mu <dzm91@hust.edu.cn>
Cc: Weijie Yuan <wy@wyuan.org>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <si.yanteng@linux.dev>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to attempt to gradually eliminate the compilation output?
Date: Wed, 04 Nov 2026 00:20:14 -0700	[thread overview]
Message-ID: <87y0b99i6p.fsf@trenco.lwn.net> (raw)
In-Reply-To: <aurU4uKyIUBl9-CJ@wyuan.org>

Weijie Yuan <kernel@wyuan.org> writes:

> Recently I've sent several patches to fix warnings.  But since I am not
> familiar with the actual codes of theirs, I'm not confident enough to
> touch some parts, but only the most obvious ones.
>
> Since this is a goal that Jon has spent years for, I'm wondering if it's
> possible to periodically send out some email notifications, which will
> use the file paths from the compiled output to find the recipients and
> kindly ask them to to deal with these annoying outputs? Perhaps we could
> use a script to do this.?

I think that nagging others to fix warnings is not going to make anybody
happy.  The best we can do in that regard is to try to prevent the
addition of new ones.  Beyond that, it is far better to send a patch
than a request for somebody else to make one.  If nothing else, an
incorrect patch is usually the best way to get somebody else to create a
correct one :)

Thanks,

jon

  reply	other threads:[~2026-11-04  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  6:46 Weijie Yuan
2026-11-04  7:20 ` Jonathan Corbet [this message]
2026-11-04  8:14   ` Weijie Yuan
2026-11-04  8:42     ` Jonathan Corbet
2026-11-04  8:56       ` Weijie Yuan

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=87y0b99i6p.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=dzm91@hust.edu.cn \
    --cc=kernel@wyuan.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=wy@wyuan.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

all inboxes | Powered by JetHome®