Linux Documentation
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Andreas Kemnade <andreas@kemnade.info>,
	Karl Mehltretter <kmehltretter@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-doc@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Steve Wahl <steve.wahl@hpe.com>,
	Dimitri Sivanich <dimitri.sivanich@hpe.com>,
	Mike Travis <mike.travis@hpe.com>,
	Tony Luck <tony.luck@intel.com>,
	linux-edac@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Tony Lindgren <tony@atomide.com>,
	Kevin Hilman <khilman@baylibre.com>,
	linux-omap@vger.kernel.org,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	Damien Le Moal <dlemoal@kernel.org>,
	Niklas Cassel <cassel@kernel.org>,
	linux-ide@vger.kernel.org,
	Ethan Nelson-Moore <enelsonmoore@gmail.com>,
	Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: [PATCH v2 3/9] docs: kernel-parameters: Drop the edac_report= entry
Date: Sat, 5 Sep 2026 11:50:37 -0700	[thread overview]
Message-ID: <20260905185037.GDapxkfbPNUxJgaMH8@fat_crate.local> (raw)
In-Reply-To: <20260905194720.7033b956@kemnade.info>

On Sat, Sep 05, 2026 at 07:47:20PM +0200, Andreas Kemnade wrote:
> > That's for "not getting any answers" which is not the case here.

No, that's the case ALWAYS. If you spam maintainers with too often
submissions, you end up achieving the opposite to what you're trying to do.

If you spam me way too often, I will send you to /dev/null because you're not
the only one who needs attention. Just imagine you're on the receiving end of
multiple tens of patchsets at any given time and everyone needs to have
her/his reviewed first. You'll do the same.

> > Sending a vX update sometimes feels more urgent because you don't want other 
> > people to read your buggy old version.

That's not a problem - everyone sees when it is buggy and if it is not clear,
you can respond to yourself and say that it'll be fixed in the next one. We
all have done it - no problem there. And if you document it, everyone is clear
what's going on.

> > But yes, some patience is also good there. 

With the amount of work all maintainers are swamped with and no one really
helping them out with patch review and testing, patience is the only virtue
here.

> Well, here it is a bit border line. You do not have answers on all patches,
> so technically it is some resubmitting.
> 
> But if the main maintainers (which is a bit harder to say in this series) found
> time to review, than IMHO (also seen from my maintainer perspective), improve
> as soon as you find time and submit the improved version.

If you want an earlier submission, feel free to ask the person.

In the general case, though, one should do a good testing before submitting
and all the issues caught after that, one can work in in her/his next version
locally and perhaps even state so.

Maintainers feel a lot better about a patchset when the whole evolution of the
patches is done on the mailing list and is documented. But shooting out a new
pile every day is just too fast, too much, too unnecessary.

I sincerely hope that explains it better.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2026-09-05 18:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05  9:46 [PATCH v2 0/9] docs: kernel-parameters: Remove ten entries for parameters that no longer exist Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 1/9] docs: kernel-parameters: Drop the atarimouse= entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 2/9] docs: kernel-parameters: Drop the bau= entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 3/9] docs: kernel-parameters: Drop the edac_report= entry Karl Mehltretter
2026-09-05 15:13   ` Borislav Petkov
2026-09-05 15:22     ` Karl Mehltretter
2026-09-05 15:33       ` Borislav Petkov
2026-09-05 16:20         ` Jonathan Corbet
2026-09-05 16:27           ` Borislav Petkov
2026-09-05 16:45             ` Karl Mehltretter
2026-09-05 17:47               ` Andreas Kemnade
2026-09-05 18:50                 ` Borislav Petkov [this message]
2026-09-06  8:19                   ` Andreas Kemnade
2026-09-05  9:46 ` [PATCH v2 4/9] docs: kernel-parameters: Drop the enable_timer_pin_1 entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 5/9] docs: kernel-parameters: Drop the mini2440= entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 6/9] docs: kernel-parameters: Drop the nomfgpt entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 7/9] docs: kernel-parameters: Drop the omap_mux= entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 8/9] docs: kernel-parameters: Drop the pcmv= entry Karl Mehltretter
2026-09-05  9:46 ` [PATCH v2 9/9] docs: kernel-parameters: Drop the pata_legacy.qdi and pata_legacy.winbond entries Karl Mehltretter
2026-09-05 12:29   ` Karl Mehltretter
2026-09-05 10:12 ` [PATCH v2 0/9] docs: kernel-parameters: Remove ten entries for parameters that no longer exist Arnd Bergmann
2026-09-05 12:25   ` Karl Mehltretter
2026-09-06  3:58 ` Randy Dunlap

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=20260905185037.GDapxkfbPNUxJgaMH8@fat_crate.local \
    --to=bp@alien8.de \
    --cc=andreas@kemnade.info \
    --cc=arnd@arndb.de \
    --cc=cassel@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=dlemoal@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=enelsonmoore@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=khilman@baylibre.com \
    --cc=kmehltretter@gmail.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=mike.travis@hpe.com \
    --cc=mingo@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=schmitzmic@gmail.com \
    --cc=skhan@linuxfoundation.org \
    --cc=steve.wahl@hpe.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=tony@atomide.com \
    --cc=x86@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