Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 10 Sep 2018 19:02:43 +0200 (CEST)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     =?ISO-8859-15?Q?Ville_Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
cc:     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"
In-Reply-To: <20180910164631.GV5565@intel.com>
Message-ID: <alpine.DEB.2.21.1809101857510.1419@nanos.tec.linutronix.de>
References: <20180910121925.27682-1-ville.syrjala@linux.intel.com> <alpine.DEB.2.21.1809101443290.1292@nanos.tec.linutronix.de> <20180910140710.GR5565@intel.com> <alpine.DEB.2.21.1809101816320.1419@nanos.tec.linutronix.de> <20180910164631.GV5565@intel.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1759614852-1536598964=:1419"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1759614852-1536598964=:1419
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT

On Mon, 10 Sep 2018, Ville Syrj?l? wrote:
> On Mon, Sep 10, 2018 at 06:23:49PM +0200, Thomas Gleixner wrote:
> > 1) My workflow makes things tagged as BUG and REGRESSION urgent
> >    automatically while [PATCH] just is queued to the normal pile of
> >    backlog, i.e. at the end. It just sprang into my eyes by chance, but in
> >    general you might just get the contrary of what you are looking for.
> 
> Ah. Might be nice to document that somewhere. I might have to type up
> that git-regression tool for myself, because I'm lazy.

Well, it's probably different between maintainers, but it's common practice
to have '[REGRESION] sub/sys got fubarred' in the subject.

> > 2) A proper bug report with proper information (it's documented what should
> >    be provided), is way more worth than a patch with a mostly useless
> >    change log, which forces me to ask for the proper information instead of
> >    having it right away.
> 
> I do agree that not having to ask for more information would be nice,
> but hard to generalize because every subsystem needs different things.
> 
> In this case you asked for the dmesg, which isn't even mentioned in
> Documentation/admin-guide/reporting-bugs.rst as far as I can see.
> So I'm not quite sure which documentation you're referring to here.

I didn't look, but I expected dmesg to be part of it and a lot of people
provide it as well as the start point of their bisection. Again, I had to
do a shot into the dark and ask you whether it's fixed in -rc3. bisect
start would have told me.

So again. That revert patch habit does not make my life easier at all.

Thanks,

	tglx
--8323329-1759614852-1536598964=:1419--