From: Matthew Wilcox <willy@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Tri Vo <trong@android.com>, Randy Dunlap <rdunlap@infradead.org>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Hackmann <ghackmann@android.com>,
Linux Memory Management List <linux-mm@kvack.org>,
kbuild-all@01.org, kbuild test robot <lkp@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] gcov: fix when CONFIG_MODULES is not set
Date: Wed, 3 Apr 2019 08:24:07 -0700 [thread overview]
Message-ID: <20190403152407.GG22763@bombadil.infradead.org> (raw)
In-Reply-To: <CAKwvOd=PstHEm_Vxtx_SGanKhAJSjoQiCb3kgCVeK4peUF2k-g@mail.gmail.com>
On Tue, Apr 02, 2019 at 09:54:50AM +0700, Nick Desaulniers wrote:
> Looks like the format is:
> Fixes: <first 12 characters of commit sha> ("<first line of commit>")
> so:
> Fixes: 8c3d220cb6b5 ("gcov: clang support")
>
> We should update:
> https://www.kernel.org/doc/html/v5.0/process/stable-kernel-rules.html
> to include this information.
It's in Documentation/process/submitting-patches.rst already.
prev parent reply other threads:[~2019-04-03 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 8:06 [linux-next:master 4291/4370] kernel/gcov/gcc_4_7.c:162:9: error: implicit declaration of function 'within_module'; did you mean 'init_module'? kbuild test robot
2019-03-29 17:45 ` [PATCH] gcov: include linux/module.h for within_module Nick Desaulniers
2019-03-29 18:01 ` Randy Dunlap
2019-03-29 18:08 ` Randy Dunlap
2019-03-29 18:09 ` Nick Desaulniers
2019-03-29 18:10 ` Randy Dunlap
2019-03-29 18:18 ` [PATCH v2] gcov: fix when CONFIG_MODULES is not set Nick Desaulniers
2019-03-29 20:53 ` Randy Dunlap
2019-03-30 23:57 ` Tri Vo
2019-04-02 2:54 ` Nick Desaulniers
2019-04-03 15:24 ` Matthew Wilcox [this message]
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=20190403152407.GG22763@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ghackmann@android.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.com \
--cc=oberpar@linux.ibm.com \
--cc=rdunlap@infradead.org \
--cc=trong@android.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;
as well as URLs for NNTP newsgroup(s).