From: Kay Sievers <kay.sievers@vrfy.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
johnstul@us.ibm.com, davidel@xmailserver.org, virtuoso@slind.org,
tglx@linutronix.de, chris.friesen@genband.com,
kirill@shutemov.name, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set
Date: Wed, 11 May 2011 17:44:01 +0200 [thread overview]
Message-ID: <BANLkTi==fti+0ABXscjRCT5JUnfy0eH63g@mail.gmail.com> (raw)
In-Reply-To: <1305127885.2914.241.camel@laptop>
On Wed, May 11, 2011 at 17:31, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, 2011-05-11 at 17:17 +0200, Kay Sievers wrote:
>>
>> If you think that needs to change, please discuss/provide
>> alternatives, which we can check if they sufficiently work for us,
>> like we did with this patch.
>
> Since this is a published interface that's not the way things work,
> first thing is to revert this to avoid us getting stuck with this crap.
What? That is not merged. Anything that would need fixing can still be
fixed. But I guess you need to do more than just calling it 'crap'.
>> But please stop rhetorically asking me if I want a slower kernel, and
>> chance your tone. That will get us nowhere.
>
> Ah, we've got our patch and we'll stick to it no matter what the
> consequences,
> very good attitude that.
It's not my patch. I just like its interface very much.
Kay
prev parent reply other threads:[~2011-05-11 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-99ee5315dac6211e972fa3f23bcc9a0343ff58c4@git.kernel.org>
2011-05-11 10:23 ` [tip:timers/core] timerfd: Allow timers to be cancelled when clock was set Peter Zijlstra
2011-05-11 11:58 ` Kay Sievers
2011-05-11 13:45 ` Peter Zijlstra
2011-05-11 13:52 ` Kay Sievers
2011-05-11 14:01 ` Peter Zijlstra
2011-05-11 14:22 ` Kay Sievers
2011-05-11 14:30 ` Peter Zijlstra
2011-05-11 14:32 ` Kay Sievers
2011-05-11 14:48 ` Peter Zijlstra
2011-05-11 14:53 ` Kay Sievers
2011-05-11 15:11 ` Peter Zijlstra
2011-05-11 15:17 ` Kay Sievers
2011-05-11 15:31 ` Peter Zijlstra
2011-05-11 15:44 ` Kay Sievers [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='BANLkTi==fti+0ABXscjRCT5JUnfy0eH63g@mail.gmail.com' \
--to=kay.sievers@vrfy.org \
--cc=chris.friesen@genband.com \
--cc=davidel@xmailserver.org \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=virtuoso@slind.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox