All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] osdep: Less restrictive F_SEFL in qemu_dup_flags()
Date: Tue, 23 Oct 2012 16:37:36 +0200	[thread overview]
Message-ID: <5086ABB0.5060506@redhat.com> (raw)
In-Reply-To: <1350592864-10408-1-git-send-email-coreyb@linux.vnet.ibm.com>

Am 18.10.2012 22:41, schrieb Corey Bryant:
> qemu_dup_flags() currently limits the flags that can be set on the
> fcntl() F_SETFL call to those that we currently know can be set with
> fcntl() F_SETFL.  The problem with this is that it will prevent use
> of new flags in the future without a code update.
> 
> This patch relaxes the checking and lets fcntl() determine the flags
> it can set.
> 
> Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>

Thanks, applied to the block branch.

Kevin

      reply	other threads:[~2012-10-23 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 20:41 [Qemu-devel] [PATCH] osdep: Less restrictive F_SEFL in qemu_dup_flags() Corey Bryant
2012-10-23 14:37 ` Kevin Wolf [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=5086ABB0.5060506@redhat.com \
    --to=kwolf@redhat.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.