stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Kees Cook <keescook@chromium.org>, Greg KH <greg@kroah.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	stable <stable@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [stable] Removing or restricting timer_stats
Date: Wed, 19 Apr 2017 08:25:53 -0700	[thread overview]
Message-ID: <6ab4a1c1-d052-a3ee-eaba-3494ece40773@linux.intel.com> (raw)
In-Reply-To: <CAGXu5jKz54R1Tc+yBRrhJdndXabzKpXid_po9gHMHw5EzYBvdA@mail.gmail.com>

On 4/19/2017 8:01 AM, Kees Cook wrote:

>>>
>>> Arjan said it would break powertop, IIRC.
>>
>> So we broke it in 4.11?  That doesn't seem to sound reasonable, how are
>> you getting away with that?  :)
>
> tglx seemed to think that the same information was available elsewhere?

tglx was working on patches to make the same information available elsewhere *in the future*.

unless you also backport that work (and wait for powertop to release/etc)...
just backporting the interface break without backporting the new interface... leaves things stuck.

  parent reply	other threads:[~2017-04-19 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  2:25 [stable] Removing or restricting timer_stats Ben Hutchings
2017-04-18  3:38 ` Kees Cook
2017-04-19 11:50 ` Greg KH
2017-04-19 14:54   ` Kees Cook
2017-04-19 14:57     ` Greg KH
2017-04-19 15:01       ` Kees Cook
2017-04-19 15:18         ` Greg KH
2017-04-19 15:25         ` Arjan van de Ven [this message]
2017-04-19 15:37           ` Greg KH
2017-04-19 16:20             ` Kees Cook

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=6ab4a1c1-d052-a3ee-eaba-3494ece40773@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=ben@decadent.org.uk \
    --cc=greg@kroah.com \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).