From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failures after merge of the keys tree
Date: Thu, 9 Jan 2020 13:22:40 +1100 [thread overview]
Message-ID: <20200109132240.264728ef@canb.auug.org.au> (raw)
In-Reply-To: <20191212115901.221d8ba1@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
Hi David,
On Thu, 12 Dec 2019 11:59:01 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the keys tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
....
> Caused by commit
>
> 068df091816a ("keys: Replace uid/gid/perm permissions checking with an ACL")
>
> I have used the keys tree from next-20191211 for today.
Any ETA on when this tree will be updated?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-09 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 0:59 linux-next: build failures after merge of the keys tree Stephen Rothwell
2020-01-09 2:22 ` Stephen Rothwell [this message]
2020-01-16 20:47 ` David Howells
2020-01-16 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=20200109132240.264728ef@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).