From: Borislav Petkov <bp@alien8.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Dou Liyang <douly.fnst@cn.fujitsu.com>,
Pavel Tatashin <pasha.tatashin@microsoft.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] Revert "x86/tsc: Consolidate init code"
Date: Mon, 10 Sep 2018 17:25:38 +0200 [thread overview]
Message-ID: <20180910152538.GA4386@zn.tnic> (raw)
In-Reply-To: <20180910150910.GS5565@intel.com>
On Mon, Sep 10, 2018 at 06:09:10PM +0300, Ville Syrjälä wrote:
> But it is a patch, and if it happens to get accepted as is so be
> it. If not, it's a good place where to start the conversation on
> how to fix the bug in another way.
Uh, more of that "logic".
It is a patch but not really, if it is applied, good, if not, also good.
WTF dude?
> You guys seem to have a notion that anything which says '[PATCH]'
> is somehow final. In my book any patch is up for debate. Nothing
> special about this one in that regard.
Well, let's see: imagine you're a maintainer. You get gazillion patches
a day. And you think, oh well, I need to review and possibly apply this.
And then move on to the next one. Because everyone is asking, when is
she/he going to apply my damn patches...
But nooo, *some* of the patches are special - they're a conversation
starter *only*! But also if applied, that's fine too.
What a bunch of bull!
What's wrong with sending a mail tagged with "[REGRESSION]" - this looks
like the tag people have adopted - and explain what the problem is, what
you've bisected it to and what your observations are? Like everyone else
reporting bugs/regressions/...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-09-10 15:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 12:19 [PATCH] Revert "x86/tsc: Consolidate init code" Ville Syrjala
2018-09-10 12:48 ` Thomas Gleixner
2018-09-10 13:19 ` Pasha Tatashin
2018-09-10 14:07 ` Ville Syrjälä
2018-09-10 14:47 ` Borislav Petkov
2018-09-10 15:09 ` Ville Syrjälä
2018-09-10 15:25 ` Borislav Petkov [this message]
2018-09-10 15:51 ` Ville Syrjälä
2018-09-10 16:06 ` Borislav Petkov
2018-09-10 16:23 ` Thomas Gleixner
2018-09-10 16:46 ` Ville Syrjälä
2018-09-10 17:02 ` Thomas Gleixner
2018-09-11 12:16 ` Ville Syrjälä
2018-09-10 16:53 ` Thomas Gleixner
2018-09-11 12:15 ` Ville Syrjälä
2018-09-11 20:56 ` Thomas Gleixner
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=20180910152538.GA4386@zn.tnic \
--to=bp@alien8.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@microsoft.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=ville.syrjala@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.