From: David Howells <dhowells@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: dhowells@redhat.com, kbuild-all@01.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jlayton@redhat.com, mszeredi@redhat.com
Subject: Re: [PATCH] VFS: Differentiate mount flags (MS_*) from internal superblock flags
Date: Wed, 14 Jun 2017 15:56:56 +0100 [thread overview]
Message-ID: <10208.1497452216@warthog.procyon.org.uk> (raw)
In-Reply-To: <201706110108.06cQbzCU%fengguang.wu@intel.com>
kbuild test robot <lkp@intel.com> wrote:
> >> fs/cifs/cifsglob.h:561:9: note: in expansion of macro 'SB_NOEXEC'
> SB_NOEXEC | SB_NOSUID | SB_NODEV)
There's a missing '|' before SB_NOEXEC at the end of the preceding line.
David
next prev parent reply other threads:[~2017-06-14 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:01 [PATCH] VFS: Differentiate mount flags (MS_*) from internal superblock flags David Howells
2017-06-09 15:33 ` Jeff Layton
2017-06-09 16:04 ` David Howells
2017-06-10 17:15 ` kbuild test robot
2017-06-14 14:56 ` David Howells [this message]
2017-06-10 17:59 ` kbuild test robot
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=10208.1497452216@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mszeredi@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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