mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: mtk.manpages@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] timerfd add flags check
Date: Wed, 11 Feb 2009 11:35:55 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0902111133410.25076@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <cfd18e0f0902102042i677322d3t32ccb7d3a8d5659@mail.gmail.com>

On Wed, 11 Feb 2009, Michael Kerrisk wrote:

> On Tue, Feb 10, 2009 at 1:36 PM, Michael Kerrisk
> <mtk.manpages@googlemail.com> wrote:
> > On Tue, Feb 10, 2009 at 12:31 PM, Davide Libenzi
> > <davidel@xmailserver.org> wrote:
> >> Like Michael requested, this patch adds a missing check for valid flags in
> >> timerfd_settime(), and make it return EINVAL in case some extra bits are
> >> set.
> >>
> >> Michael said:
> >> If this is to be any use to userland apps that want to check flag
> >> support (perhaps it is too late already), then the sooner we get it
> >> into the kernel the better: 2.6.29 would be good; earlier stables as
> >> well would be even better.
> >>
> >> Acked-by: Michael Kerrisk <mtk.manpages@gmail.com>
> >>
> >>
> >> Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
> >
> > Davide, one question: is the TFD_FLAGS_SET constant below needed?
> 
> Davide, Ping!  I see Andrew already took the patch, which seems to
> define this unnecessary macro.

Yes, Michael! I will post a correction to Andrew. OTOH an un-necessary 
macro defined could even be passed into the lower priority queue, don't 
you think?



- Davide



      reply	other threads:[~2009-02-11 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 23:31 Davide Libenzi
2009-02-10  0:36 ` Michael Kerrisk
2009-02-11  4:42   ` Michael Kerrisk
2009-02-11 19:35     ` Davide Libenzi [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=alpine.DEB.1.10.0902111133410.25076@alien.or.mcafeemobile.com \
    --to=davidel@xmailserver.org \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.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

all inboxes | Powered by JetHome®