From: Seebs <seebs@seebs.net>
To: Will Page <Will.Page@ni.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [pseudo][PATCH] Fix to fcntl guts to ignore flags that can be ORed into cmd
Date: Fri, 15 Sep 2017 18:10:20 -0500 [thread overview]
Message-ID: <20170915181020.6a184e6a@seebsdell> (raw)
In-Reply-To: <20170915222700.GA15457@canismajor>
On Fri, 15 Sep 2017 15:27:00 -0700
Will Page <Will.Page@ni.com> wrote:
> The fcntl guts switch on "cmd" parameter to identify the fcntl
> command being issued, but isn't aware of the file creation flags that
> can be ORed in.
This is true. I was, in fact, not aware of those flags. Looks
reasonable.
-s
next prev parent reply other threads:[~2017-09-15 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 22:27 [pseudo][PATCH] Fix to fcntl guts to ignore flags that can be ORed into cmd Will Page
2017-09-15 22:30 ` ✗ patchtest: failure for " Patchwork
2017-09-15 22:48 ` [pseudo][PATCH] " Burton, Ross
2017-09-16 2:22 ` Will Page
2017-09-16 17:59 ` Seebs
2017-09-15 23:10 ` Seebs [this message]
2017-09-18 13:24 ` Richard Purdie
2017-09-18 15:15 ` Will Page
2017-09-18 15:39 ` Will Page
-- strict thread matches above, loose matches on Subject: below --
2017-09-16 2:33 Will Page
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=20170915181020.6a184e6a@seebsdell \
--to=seebs@seebs.net \
--cc=Will.Page@ni.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.