From: Thomas Gleixner <tglx@linutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: linux-next: Fixes tag needs some work in the tip tree
Date: Fri, 18 Jan 2019 00:45:44 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1901180044260.1647@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190118093135.39cf071e@canb.auug.org.au>
On Fri, 18 Jan 2019, Stephen Rothwell wrote:
> Commit
>
> a31e184e4f69 ("x86/pkeys: Properly copy pkey state at fork()")
>
> Fixes tag
>
> Fixes: e8c24d3a23a ("x86/pkeys: Allocation/free syscalls")
>
> has these problems:
>
> - SHA1 should be at least 12 digits long
Sigh. I'll add that to my sanity checks, but this one has to be as is as
it's in the middle of a series of fixes pending for linus tree.
Thanks,
tglx
next prev parent reply other threads:[~2019-01-17 23:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 22:31 linux-next: Fixes tag needs some work in the tip tree Stephen Rothwell
2019-01-17 23:45 ` Thomas Gleixner [this message]
2019-01-18 0:32 ` Stephen Rothwell
2019-01-18 1:19 ` Joe Perches
2019-01-17 22:35 Stephen Rothwell
2019-01-17 23:19 ` Thomas Gleixner
2019-02-10 20:36 Stephen Rothwell
2019-02-11 7:17 ` Ingo Molnar
2019-04-25 21:09 Stephen Rothwell
2019-05-03 10:22 Stephen Rothwell
2019-06-22 14:06 Stephen Rothwell
2019-08-25 13:31 Stephen Rothwell
2019-08-28 22:06 Stephen Rothwell
2019-08-29 8:26 ` Bandan Das
2019-08-29 9:18 ` Stephen Rothwell
2020-03-24 20:44 Stephen Rothwell
2020-08-20 6:12 Stephen Rothwell
2020-08-20 8:21 ` Borislav Petkov
2020-08-20 9:15 ` Stephen Rothwell
2020-08-20 9:20 ` Borislav Petkov
2020-08-20 9:22 ` David Sterba
2020-08-20 9:26 ` Borislav Petkov
2020-09-30 12:52 Stephen Rothwell
2020-09-30 12:53 Stephen Rothwell
2020-10-28 10:19 Stephen Rothwell
2020-11-08 21:43 Stephen Rothwell
2020-11-22 10:06 Stephen Rothwell
2021-03-01 20:28 Stephen Rothwell
2021-03-28 21:30 Stephen Rothwell
2021-03-28 22:56 ` Masami Hiramatsu
2021-05-08 2:18 Stephen Rothwell
2021-05-08 10:02 ` Song Bao Hua (Barry Song)
2021-05-20 11:50 Stephen Rothwell
2021-06-24 11:16 Stephen Rothwell
2021-11-25 21:17 Stephen Rothwell
2021-12-16 18:49 Stephen Rothwell
2022-04-09 5:23 Stephen Rothwell
2022-05-12 10:49 Stephen Rothwell
2022-05-22 0:46 Stephen Rothwell
2024-02-27 21:03 Stephen Rothwell
2024-03-14 21:09 Stephen Rothwell
2024-03-15 14:29 ` Thomas Gleixner
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=alpine.DEB.2.21.1901180044260.1647@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.