From: Borislav Petkov <bp@suse.de>
To: Mike Travis <mike.travis@hpe.com>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Steve Wahl <steve.wahl@hpe.com>,
Yang Li <yang.lee@linux.alibaba.com>
Subject: Re: arch/x86/kernel/apic/x2apic_uv_x.c:106 early_get_pnodeid() warn: inconsistent indenting
Date: Thu, 22 Apr 2021 11:06:52 +0200 [thread overview]
Message-ID: <20210422090652.GB6361@zn.tnic> (raw)
In-Reply-To: <84b4fbc3-0310-b7d7-f613-0eb4ae090e1e@hpe.com>
On Wed, Apr 21, 2021 at 06:38:37PM -0700, Mike Travis wrote:
> I'm a bit confused. I have this in my inbox that someone else has this fix.
> So will that fix be applied or should I send a separate one that is
> essentially a duplicate?
I'm not even considering that fix because I'm tired of getting some
half-baked robot mails which only resemble patches. The obnoxiousness to
not have the decency to sit down and write a proper commit message is
getting totally out of control.
Apparently some people(?) think that sending robot output to real humans
*without* even vetting that output is a good idea so off to /dev/null it
goes.
If you want this fixed, you could do a proper patch with a sensible
commit message and I'll take it.
I'm tired of dumb robots.
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2021-04-22 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 11:03 arch/x86/kernel/apic/x2apic_uv_x.c:106 early_get_pnodeid() warn: inconsistent indenting kernel test robot
2021-04-22 1:38 ` Mike Travis
2021-04-22 9:06 ` Borislav Petkov [this message]
2021-04-22 21:50 ` Mike Travis
2021-04-22 21:56 ` Borislav Petkov
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=20210422090652.GB6361@zn.tnic \
--to=bp@suse.de \
--cc=dimitri.sivanich@hpe.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mike.travis@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=yang.lee@linux.alibaba.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