From: Casey Schaufler <casey@schaufler-ca.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: linux-next: Tree for Jan 29 (security/smack/)
Date: Wed, 29 Jan 2020 14:54:09 -0800 [thread overview]
Message-ID: <3ac1c817-b310-c8f8-6990-1602db540106@schaufler-ca.com> (raw)
In-Reply-To: <e66a563e-b612-c5b6-7bdd-b55113a9b822@infradead.org>
On 1/29/2020 2:18 PM, Randy Dunlap wrote:
> On 1/28/20 8:54 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v5.7 material to your linux-next included
>> branches until after v5.6-rc1 has been released.
>>
>> Changes since 20200128:
>>
This keeps coming up. It's in David Howells' watch queue changes.
David, could you please fix this?
> ../security/smack/smack_lsm.c: In function �smack_post_notification�:
> ../security/smack/smack_lsm.c:4383:7: error: dereferencing pointer to incomplete type �struct watch_notification�
> if (n->type == WATCH_TYPE_META)
> ^~
> CC kernel/time/hrtimer.o
> ../security/smack/smack_lsm.c:4383:17: error: �WATCH_TYPE_META� undeclared (first use in this function); did you mean �TCA_PIE_BETA�?
> if (n->type == WATCH_TYPE_META)
> ^~~~~~~~~~~~~~~
> TCA_PIE_BETA
>
>
> Probably just missing
> #include <linux/watch_queue.h>
>
>
next prev parent reply other threads:[~2020-01-29 22:54 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 [this message]
2020-01-31 17:35 ` David Howells
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=3ac1c817-b310-c8f8-6990-1602db540106@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=dhowells@redhat.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).