From: Changbin Du <changbin.du@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Changbin Du <changbin.du@gmail.com>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: Re: linux-next: Fixes tag needs some work in Linus' tree
Date: Tue, 19 Feb 2019 01:58:43 +0000 [thread overview]
Message-ID: <20190219015842.tkdahxo24wnu35nh@mail.google.com> (raw)
In-Reply-To: <20190219073345.11c39f70@canb.auug.org.au>
On Tue, Feb 19, 2019 at 07:33:45AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> [Just a note for some future improvement]
>
> In commit
>
> 2c4f1fcbef0b ("kprobe: Do not use uaccess functions to access kernel memory that can fault")
>
> Fixes tag
>
> Fixes: 9da3f2b7405 ("x86/fault: BUG() when uaccess helpers fault on kernel addresses")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
>
> --
Thanks for reminding. The scripts/checkpatch.pl does has such check but
it only checks the commit message body. I will try to extend it to
include tags, and hint how to configure git.
> Cheers,
> Stephen Rothwell
--
Cheers,
Changbin Du
next prev parent reply other threads:[~2019-02-19 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 20:33 linux-next: Fixes tag needs some work in Linus' tree Stephen Rothwell
2019-02-19 1:58 ` Changbin Du [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-21 2:10 Stephen Rothwell
2019-02-21 20:16 Stephen Rothwell
2019-02-20 20:38 Stephen Rothwell
2019-02-20 21:36 ` David Howells
2019-02-02 21:28 Stephen Rothwell
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=20190219015842.tkdahxo24wnu35nh@mail.google.com \
--to=changbin.du@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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