# Re: \[PATCH v2 3/9\] docs: kernel-parameters: Drop the edac\_report= entry

- From: Andreas Kemnade \<andreas@kemnade.info\>
- Date: 2026-09-06 08:19:52 
- List: linux-input
- Page: https://ratatoskr.run/linux-input/2026/09/17520269
- Thread: https://ratatoskr.run/linux-input/2026/09/17518279/t.md

```text
On Sat, 5 Sep 2026 11:50:37 -0700
Borislav Petkov [ref] wrote:

> 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.
>
This particular set was sent too fast, I agree, but reading that document again, it
sounds like the summary is being patient with busy people.

Some subsystems even discourage waiting in such cases:
e.g.
https://docs.kernel.org/process/maintainer-netdev.html
"Do not wait too long (weeks) between postings either as it will make it
harder for reviewers to recall all the context."

[...] 
> > 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.
> 
Hmm, maybe I was misunderstood. Just to avoid that I accidentially provoke
patch-flooding with my comments:
The next revision should come only after you have finished your homework
(improve according to review comments, tests,...) and any further review
comments are unlikely.

Regards,
Andreas
```
