mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	David Sharp <dhsharp@google.com>,
	Vaibhav Nagarnaik <vnagarnaik@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] tracing: Remove useless 4 bytes of padding from every event
Date: Wed, 16 May 2012 16:13:46 -0400	[thread overview]
Message-ID: <1337199226.6724.84.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4FB408F2.8060002@linux.intel.com>

On Wed, 2012-05-16 at 13:07 -0700, Arjan van de Ven wrote:
> On 5/16/2012 1:04 PM, Linus Torvalds wrote:
> > On Wed, May 16, 2012 at 1:00 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> >>
> >> Seriously though. What's your take on changing the kernel that will
> >> break an older distro. Obviously, this change is too early to apply. But
> >> because an old distro has one app that will break if we make a change in
> >> the kernel, is that enough to keep that change out?
> > 
> > I suspect that powertop is enough of a developer thing that if that's
> > the only thing that breaks, we don't have to worry too much.
> > 
> > I don't want to break *everybody*, so new distro's should be
> > up-to-date. But breaking something like a F14-15 timeframe distro or
> > something staid like a SLES (or "Debian Stale" or whatever they call
> > that thing that only takes crazy-old binaries)? It's fine. We don't
> > want to *rush* into it, but no, if those distros are basically not
> > updating, we can't care about them forever for something like
> > powertop.
> 
> agreed.
> 
> I would say something like "6 months" (e.g. 3.6); anybody who's likely
> to update anything will have done the powertop upgrade from his distro
> by then, and anybody who isn't isn't going to update the kernel either.
> 

Thanks for the clarification. I'll put the patch in my 3.6 or 3.7 queue.

-- Steve



  reply	other threads:[~2012-05-16 20:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:44 Steven Rostedt
2012-05-16 17:24 ` [RFC][PATCH v2] " Steven Rostedt
2012-05-16 19:33 ` [RFC][PATCH] " Linus Torvalds
2012-05-16 19:36   ` Arjan van de Ven
2012-05-16 19:47     ` Steven Rostedt
2012-05-16 19:51     ` Linus Torvalds
2012-05-16 20:03       ` Steven Rostedt
2012-05-17  8:04         ` Ingo Molnar
2012-05-16 20:00   ` Steven Rostedt
2012-05-16 20:04     ` Linus Torvalds
2012-05-16 20:07       ` Arjan van de Ven
2012-05-16 20:13         ` Steven Rostedt [this message]
2012-05-16 20:14         ` Dave Jones
2012-05-16 20:16           ` Arjan van de Ven
2012-05-17  8:06             ` Ingo Molnar
2012-05-17 12:11               ` Steven Rostedt

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=1337199226.6724.84.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=dhsharp@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vnagarnaik@google.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®