From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the keys tree
Date: Mon, 13 Nov 2017 09:42:32 +0000 [thread overview]
Message-ID: <31589.1510566152@warthog.procyon.org.uk> (raw)
In-Reply-To: <20171113131056.14b3f4da@canb.auug.org.au>
I've dropped the keyrings ACL patches for now and repushed the branch. I'll
wait till after the merge window before pushing them again (with their fixes).
David
next prev parent reply other threads:[~2017-11-13 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 2:10 linux-next: build warnings after merge of the keys tree Stephen Rothwell
2017-11-13 9:42 ` David Howells [this message]
2019-07-30 2:30 Stephen Rothwell
2019-07-30 3:47 ` Eric Biggers
2019-07-30 3:52 ` Stephen Rothwell
2019-07-31 1:40 ` Eric Biggers
2019-07-31 3:05 ` Stephen Rothwell
2020-05-04 3:47 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=31589.1510566152@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--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 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).