From: Chuck Wolber <chuckwolber@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Brown <broonie@kernel.org>, Jiri Kosina <jkosina@suse.com>,
ksummit@lists.linux.dev,
Kate Stewart <kstewart@linuxfoundation.org>,
Gabriele Paoloni <gpaoloni@redhat.com>
Subject: Re: [MAINTAINERS SUMMIT] The amount of -stable emails
Date: Tue, 5 Aug 2025 17:40:10 +0000 [thread overview]
Message-ID: <CAB=6tBRUuSBo6xocUJh5oaPsiPPsg6EBjPMpyu0HxkFcs3BOpg@mail.gmail.com> (raw)
In-Reply-To: <20250805122828.68312a8d@gandalf.local.home>
On Tue, Aug 5, 2025 at 4:28 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
>
> I like to see what is happening but I just don't have the time to review
> them. But every so often, one catches my attention where I think a patch
> shouldn't be added. But that's very few and far between
OBRequirementsPlug: Documenting low level design expectations
[1][2][3] should provide a
foundation for semantic filtering. It is one thing to be faced with a
"big wall of patch" that looks
like a "big pile of work". It is a completely different game when you
can readily identify what
parts of the design that patch affects.
There is no panacea, but a stepwise improvement is definitely within reach.
..Ch:W..
[1] https://sched.co/1zfhU
[2] https://www.youtube.com/watch?v=_N3l_EEV8uM
[3] https://lpc.events/event/18/contributions/1894/
next prev parent reply other threads:[~2025-08-05 17:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 15:38 Jiri Kosina
2025-08-05 16:08 ` Mark Brown
2025-08-05 16:28 ` Steven Rostedt
2025-08-05 16:41 ` Mark Brown
2025-08-06 8:04 ` Geert Uytterhoeven
2025-08-06 10:42 ` Mark Brown
2025-08-06 12:20 ` Sasha Levin
2025-08-06 12:24 ` Mark Brown
2025-08-06 14:57 ` Theodore Ts'o
2025-08-06 21:35 ` Sasha Levin
2025-08-05 17:14 ` Sasha Levin
2025-08-05 17:59 ` Konstantin Ryabitsev
2025-08-05 21:04 ` Sasha Levin
2025-08-05 17:40 ` Chuck Wolber [this message]
2025-08-05 16:49 ` James Bottomley
2025-08-05 17:26 ` Sasha Levin
2025-08-05 17:33 ` James Bottomley
2025-08-05 18:01 ` Sasha Levin
2025-08-06 8:04 ` Greg KH
2025-08-05 17:34 ` Greg KH
2025-08-05 21:39 ` Jiri Kosina
2025-08-05 22:34 ` Martin K. Petersen
2025-08-06 5:44 ` Tomasz Figa
2025-08-06 6:27 ` Takashi Iwai
2025-08-06 7:00 ` Jiri Kosina
2025-08-06 7:08 ` Takashi Iwai
2025-08-12 17:19 ` Steven Rostedt
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='CAB=6tBRUuSBo6xocUJh5oaPsiPPsg6EBjPMpyu0HxkFcs3BOpg@mail.gmail.com' \
--to=chuckwolber@gmail.com \
--cc=broonie@kernel.org \
--cc=gpaoloni@redhat.com \
--cc=jkosina@suse.com \
--cc=kstewart@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=rostedt@goodmis.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