From: Thomas Gleixner <tglx@linutronix.de>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>,
"devi R.K" <devi.feb27@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
arul.jeniston@gmail.com
Subject: Re: [PATCH] timerfd_create.2: Included return value 0
Date: Mon, 30 Mar 2020 23:29:02 +0200 [thread overview]
Message-ID: <87wo71v8f5.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <d79b3520-77ac-199e-6576-ab9f235ac297@gmail.com>
Micheal,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
> On 3/30/20 12:50 AM, Thomas Gleixner wrote:
>> That's the reason why I rejected the attempt to mitigate that particular
>> 0 tick issue in timerfd as it would just scratch a particular itch but
>> still not provide any guarantee. So having the '0' return documented is
>> the right way to go.
>
> Thanks for the incredibly detailed follow-up Thomas (which all
> landed in my commit message). I've applied a patch almost exactly
> the same as the text I showed above (and it's pushed to Git).
"timerfd_create.2: Negetive..."
That first word after the colon looks weird :)
>> All of 2020 is a bust, I expect. Perhaps we see us at a conference
> in 2021 ;-).
Let's see how that evolves and in the worst case we can meet for a beer
once we gained antibodies one way or the other. For now let's stay safe
and all I can offer is a virtual 'Prosit' :)
Thanks,
tglx
prev parent reply other threads:[~2020-03-30 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJymdbxJNag1W0vR9Ysm7_y91HwLAu4QaSMKZbed4emT1DYvww@mail.gmail.com>
2020-03-26 8:45 ` [PATCH] timerfd_create.2: Included return value 0 Michael Kerrisk (man-pages)
[not found] ` <CAJymdbwfm7EypQfXRqWZHbfj2SKk7PCP7SMccz6bmJWSauDqPQ@mail.gmail.com>
[not found] ` <CAJymdby8pDASq5Xv7DeTJ5cq1NXPe1jUWwApxZ5o-huaEXUrjw@mail.gmail.com>
2020-03-29 21:06 ` Michael Kerrisk (man-pages)
2020-03-29 22:50 ` Thomas Gleixner
2020-03-30 21:09 ` Michael Kerrisk (man-pages)
2020-03-30 21:29 ` Thomas Gleixner [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=87wo71v8f5.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=arul.jeniston@gmail.com \
--cc=devi.feb27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@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