public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Liviu Dudau <liviu@dudau•co.uk>, Qian Cai <cai@lca•pw>
Subject: linux-next: Fixes tags needs some work in the akpm-current tree
Date: Thu, 31 Jan 2019 11:05:41 +1100	[thread overview]
Message-ID: <20190131110541.3f3a808c@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

Hi all,

In commit

  86c7502b25ed ("mm/vmalloc.c: don't dereference possible NULL pointer in __vunmap()")

Fixes tag

  Fixes: f3c01d2f3ade ("mm: vmalloc: avoid racy handling of debugobjects

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

Please do not split Fixes tags across more than 1 line.

In commit

  6e9ed490d190 ("mm/page_owner: fix for deferred struct page init")

Fixes tag

  Fixes: fe53ca54270 ("mm: use early_pfn_to_nid in page_ext_init")

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").

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2019-01-31  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  0:05 Stephen Rothwell [this message]
2019-01-31  1:51 ` linux-next: Fixes tags needs some work in the akpm-current tree Qian Cai
2019-01-31 22:51   ` Liviu Dudau
2019-01-31 22:57     ` Andrew Morton
2019-02-01  0:18       ` Liviu Dudau

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=20190131110541.3f3a808c@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=cai@lca$(echo .)pw \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=liviu@dudau$(echo .)co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox