From: David Howells <dhowells@redhat.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: dhowells@redhat.com, Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 29 (security/smack/)
Date: Fri, 31 Jan 2020 17:35:09 +0000 [thread overview]
Message-ID: <266825.1580492109@warthog.procyon.org.uk> (raw)
In-Reply-To: <3ac1c817-b310-c8f8-6990-1602db540106@schaufler-ca.com>
Casey Schaufler <casey@schaufler-ca.com> wrote:
> This keeps coming up. It's in David Howells' watch queue changes.
> David, could you please fix this?
That should be fixed now in my keys-next branch.
David
prev parent reply other threads:[~2020-01-31 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 4:54 linux-next: Tree for Jan 29 Stephen Rothwell
2020-01-29 16:30 ` linux-next: Tree for Jan 29 (drivers/infiniband/hw/mlx5/main.o) Randy Dunlap
2020-01-30 10:24 ` Leon Romanovsky
2020-01-29 22:18 ` linux-next: Tree for Jan 29 (security/smack/) Randy Dunlap
2020-01-29 22:54 ` Casey Schaufler
2020-01-31 17:35 ` David Howells [this message]
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=266825.1580492109@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdunlap@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 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).