mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 18:06:33 +0200	[thread overview]
Message-ID: <20180910160633.GB4386@zn.tnic> (raw)
In-Reply-To: <20180910155112.GT5565@intel.com>

On Mon, Sep 10, 2018 at 06:51:13PM +0300, Ville Syrjälä wrote:
> Sounds to me like the maintainer should figure out how to delegate some
> of the load a bit. Or just go on vacation and ignore all mails. I hear
> stress isn't good for you.

Bullshit.

> That's what all patches are. No should be applying unreviewed patches
> blindly.
> 
> Also often a revert is a perfect way to handle regressions. It gets
> the angry users off your back ASAP allowing you to fix the bug

More bullshit.

> Calm down. No one is out to revert all your patches.

Even more bullshit.

> Maybe you can propose a new git-regression tool then? And document that
> you want bugs reported using it? Ideally I'd say it should do almost
> exactly what git revert does except s/revert/regression/. Though I
> suppose it could include the original diff instead of the reverse.

Even even more bullshit.

> Now, how about we stop this pointless "logic" discussion and
> focus on the techinal stuff from now on?

That's the only constructive and serious thing you've said so far.
Let's.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2018-09-10 16:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 12:19 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
2018-09-10 15:51           ` Ville Syrjälä
2018-09-10 16:06             ` Borislav Petkov [this message]
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=20180910160633.GB4386@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome