From: Liviu Dudau <liviu@dudau.co.uk>
To: Qian Cai <cai@lca.pw>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tags needs some work in the akpm-current tree
Date: Thu, 31 Jan 2019 22:51:52 +0000 [thread overview]
Message-ID: <20190131225151.GA3110@bart.dudau.co.uk> (raw)
In-Reply-To: <6d110fc4-85b6-cf66-6045-dc81956ffc5c@lca.pw>
On Wed, Jan 30, 2019 at 08:51:42PM -0500, Qian Cai wrote:
>
>
> On 1/30/19 7:05 PM, Stephen Rothwell wrote:
> > 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").
> >
>
> I think it is better to replace with this version instead,
>
> https://lore.kernel.org/lkml/20190115202812.75820-1-cai@lca.pw/
That patch does not look related, afaict.
Andrew, do you want me to re-send the patch with a fixed commit log, or are you OK to
do some inline editing?
Best regards,
Liviu
--
________________________________________________________
________| |_______
\ | With enough courage, you can do without a reputation | /
\ | -- Rhett Butler | /
/ |________________________________________________________| \
/__________) (_________\
next prev parent reply other threads:[~2019-01-31 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 0:05 linux-next: Fixes tags needs some work in the akpm-current tree Stephen Rothwell
2019-01-31 1:51 ` Qian Cai
2019-01-31 22:51 ` Liviu Dudau [this message]
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=20190131225151.GA3110@bart.dudau.co.uk \
--to=liviu@dudau.co.uk \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.