From: Linus Torvalds <torvalds@linux-foundation.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: "the arch/x86 maintainers" <x86@kernel.org>,
kernel test robot <xiaolong.ye@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Matthias Kaehlcke <mka@chromium.org>,
Alexander Potapenko <glider@google.com>,
Andy Lutomirski <luto@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dmitriy Vyukov <dvyukov@google.com>,
Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [PATCH] x86/asm: Fix inline asm call constraints for GCC 4.4
Date: Thu, 28 Sep 2017 16:53:09 -0700 [thread overview]
Message-ID: <CA+55aFxkVPZRAuLQ-xOsdvLZtnJpSAWuW0zUefojSmo=uLsgTg@mail.gmail.com> (raw)
In-Reply-To: <20170928215826.6sdpmwtkiydiytim@treble>
On Thu, Sep 28, 2017 at 2:58 PM, Josh Poimboeuf <jpoimboe@redhat.com> wrote:
>
> Reported-by: kernel test robot <xiaolong.ye@intel.com>
> Fixes: f5caf621ee35 ("x86/asm: Fix inline asm call constraints for Clang")
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Side note: it's not like I personally need the credit, but in general
I really want people to pick up on who debugged the code and pointed
to the solution. That's often more of the work than the fix itself.
The kernel test robot report looked to be ignored as a "gcc-4.4 is too
old to worry about" thing. People who then step up and analyze the
problem are rare as it is. They need to be credited in the commit
logs.
We don't have any fixed format for that, but it's pretty free-form. So
we have tags like
Root-caused-by:
Diagnosed-by:
Analyzed-by:
Debugged-by:
Bisected-by:
Fix-suggested-by:
etc for giving credit to people who figured out some part of a bug
(and, having grepped for this, we also a _shitload_ of miss-spellings
of various things ;)
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: lkp@lists.01.org
Subject: Re: [PATCH] x86/asm: Fix inline asm call constraints for GCC 4.4
Date: Thu, 28 Sep 2017 16:53:09 -0700 [thread overview]
Message-ID: <CA+55aFxkVPZRAuLQ-xOsdvLZtnJpSAWuW0zUefojSmo=uLsgTg@mail.gmail.com> (raw)
In-Reply-To: <20170928215826.6sdpmwtkiydiytim@treble>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Thu, Sep 28, 2017 at 2:58 PM, Josh Poimboeuf <jpoimboe@redhat.com> wrote:
>
> Reported-by: kernel test robot <xiaolong.ye@intel.com>
> Fixes: f5caf621ee35 ("x86/asm: Fix inline asm call constraints for Clang")
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Side note: it's not like I personally need the credit, but in general
I really want people to pick up on who debugged the code and pointed
to the solution. That's often more of the work than the fix itself.
The kernel test robot report looked to be ignored as a "gcc-4.4 is too
old to worry about" thing. People who then step up and analyze the
problem are rare as it is. They need to be credited in the commit
logs.
We don't have any fixed format for that, but it's pretty free-form. So
we have tags like
Root-caused-by:
Diagnosed-by:
Analyzed-by:
Debugged-by:
Bisected-by:
Fix-suggested-by:
etc for giving credit to people who figured out some part of a bug
(and, having grepped for this, we also a _shitload_ of miss-spellings
of various things ;)
Linus
next prev parent reply other threads:[~2017-09-28 23:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 7:47 [lkp-robot] [x86/asm] f5caf621ee: PANIC:double_fault kernel test robot
2017-09-28 7:47 ` kernel test robot
2017-09-28 7:59 ` Ingo Molnar
2017-09-28 7:59 ` Ingo Molnar
2017-09-28 8:18 ` Peter Zijlstra
2017-09-28 8:18 ` Peter Zijlstra
2017-09-28 8:49 ` Ingo Molnar
2017-09-28 8:49 ` Ingo Molnar
2017-09-28 11:49 ` Peter Zijlstra
2017-09-28 11:49 ` Peter Zijlstra
2017-09-28 16:21 ` Linus Torvalds
2017-09-28 16:21 ` Linus Torvalds
2017-09-28 16:44 ` Josh Poimboeuf
2017-09-28 16:44 ` Josh Poimboeuf
2017-09-28 17:01 ` Josh Poimboeuf
2017-09-28 17:01 ` Josh Poimboeuf
2017-09-28 19:10 ` Josh Poimboeuf
2017-09-28 19:10 ` Josh Poimboeuf
2017-09-28 21:58 ` [PATCH] x86/asm: Fix inline asm call constraints for GCC 4.4 Josh Poimboeuf
2017-09-28 21:58 ` Josh Poimboeuf
2017-09-28 23:53 ` Linus Torvalds [this message]
2017-09-28 23:53 ` Linus Torvalds
2017-09-29 1:40 ` Josh Poimboeuf
2017-09-29 1:40 ` Josh Poimboeuf
2017-09-29 8:01 ` Ingo Molnar
2017-09-29 8:01 ` Ingo Molnar
2017-09-29 10:32 ` Ye Xiaolong
2017-09-29 10:32 ` Ye Xiaolong
2017-09-29 7:51 ` Ingo Molnar
2017-09-29 7:51 ` Ingo Molnar
2017-09-29 15:29 ` Arnd Bergmann
2017-09-29 15:29 ` Arnd Bergmann
2017-09-29 9:27 ` [tip:x86/urgent] " tip-bot for Josh Poimboeuf
2017-09-29 9:27 ` tip-bot for Josh Poimboeuf
2017-09-29 11:18 ` tip-bot for Josh Poimboeuf
2017-09-29 11:18 ` tip-bot for Josh Poimboeuf
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='CA+55aFxkVPZRAuLQ-xOsdvLZtnJpSAWuW0zUefojSmo=uLsgTg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@kernel.org \
--cc=miguel.bernal.marin@linux.intel.com \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiaolong.ye@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.