mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sasikantha Babu <sasikanth.v19@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [GIT pull] timer fixes for 3.4
Date: Fri, 13 Apr 2012 00:26:40 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1204130022520.2542@ionos> (raw)
In-Reply-To: <CA+55aFxg0rzpL-xCqdScxPKPMupbvteoXD1cPT-fWYpyMXoSGg@mail.gmail.com>

On Thu, 12 Apr 2012, Linus Torvalds wrote:

> On Thu, Apr 12, 2012 at 3:06 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > The itimer removal one is not strictly a fix, but I really wanted to
> > avoid a rebase of the urgent ones.
> 
> Btw, I think that setitimer NULL pointer removal commit is crap.
> 
> If people actually do rely on the NULL pointer thing, we're not
> "scheduling it for removal". And we most *definitely* aren't
> scheduling it for removal for some short timeframe like 3.6.
> 
> That's not how ABI's work. If it has become something people rely on,
> it now *is* part of the ABI, and no amount of "violates the spec"
> matters what-so-ever.
> 
> "The spec" is paper - and worthless. What people actually *do* is all
> that matters.

I ran it through all the various (outdated) distros I have handy and
the printk didn't show once.

I tried to figure out the reason for this NULL pointer thing, but
there is no trace of it on the intarwebs at all.

Thanks,

	tglx

  reply	other threads:[~2012-04-12 22:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 22:06 Thomas Gleixner
2012-04-12 22:19 ` Linus Torvalds
2012-04-12 22:26   ` Thomas Gleixner [this message]
2012-04-12 22:31     ` Linus Torvalds
2012-04-12 22:39       ` Thomas Gleixner
2012-04-12 22:46         ` Linus Torvalds
2012-04-12 23:01           ` Thomas Gleixner
2012-04-26  9:23 Thomas Gleixner

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.LFD.2.02.1204130022520.2542@ionos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=sasikanth.v19@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®