From: Dan Carpenter <dan.carpenter@oracle.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [bug report] fuse: Add posix ACL support
Date: Wed, 22 Feb 2017 17:15:48 +0300 [thread overview]
Message-ID: <20170222141548.GA4133@mwanda> (raw)
In-Reply-To: <20170221183018.GA29966@ubuntu-hedt>
On Tue, Feb 21, 2017 at 12:30:18PM -0600, Seth Forshee wrote:
> On Tue, Feb 21, 2017 at 09:14:46PM +0300, Dan Carpenter wrote:
> > Hello Seth Forshee,
> >
> > The patch 60bcc88ad185: "fuse: Add posix ACL support" from Aug 29,
> > 2016, leads to the following static checker warning:
>
> This was reported once before and is a false positive. See
> http://www.spinics.net/lists/linux-fsdevel/msg103363.html.
>
Wow... That's embarrassing. I try to check that I haven't sent them
before normally... :/
regards,
dan carpenter
next prev parent reply other threads:[~2017-02-22 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:14 [bug report] fuse: Add posix ACL support Dan Carpenter
2017-02-21 18:30 ` Seth Forshee
2017-02-22 14:15 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-25 21:31 Dan Carpenter
2016-10-26 2:37 ` Seth Forshee
2016-10-26 8:30 ` Dan Carpenter
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=20170222141548.GA4133@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
/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).