From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
John Ogness <john.ogness@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>, Jan Kara <jack@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] printk for 5.20
Date: Wed, 3 Aug 2022 12:06:57 -0400 [thread overview]
Message-ID: <20220803120657.03f35595@gandalf.local.home> (raw)
In-Reply-To: <YuqXkCZEfsSKoIX6@alley>
On Wed, 3 Aug 2022 17:43:12 +0200
Petr Mladek <pmladek@suse.com> wrote:
> On the positive side. My intuition told me that it was very controversial.
> This is why I clearly described the effect. And it was the very first
> sentence in the commit message. I think that I made it _very visible_.
Right. I do not see you doing anything to lose Linus's trust. You stated
upfront exactly what it was doing. And let Linus decide if it was right or
not. Maybe it was a misjudgment on your part. But chalk it up as a learning
experience. I personally find you a good maintainer.
-- Steve
next prev parent reply other threads:[~2022-08-03 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 15:07 [GIT PULL] printk for 5.20 Petr Mladek
2022-08-01 15:45 ` David Laight
2022-08-02 7:37 ` Petr Mladek
2022-08-03 3:19 ` Linus Torvalds
2022-08-03 14:35 ` Sebastian Andrzej Siewior
2022-08-03 14:46 ` David Laight
2022-08-03 15:43 ` Petr Mladek
2022-08-03 16:06 ` Steven Rostedt [this message]
2022-08-03 16:08 ` Linus Torvalds
2022-08-03 16:34 ` Sebastian Andrzej Siewior
2022-08-03 17:08 ` Ingo Molnar
2022-08-09 1:18 ` Thomas Gleixner
2022-08-11 13:38 ` Daniel Vetter
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=20220803120657.03f35595@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).