public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation•org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] PM / OPP: fix debugfs files for 64-bit
Date: Wed, 7 Oct 2015 18:39:34 +0100	[thread overview]
Message-ID: <20151007173934.GB10665@kroah.com> (raw)
In-Reply-To: <20151007172701.GF4557@linux>

On Wed, Oct 07, 2015 at 10:57:01PM +0530, Viresh Kumar wrote:
> On 07-10-15, 18:19, Greg Kroah-Hartman wrote:
> > Ok, then stop exporting it in debugfs and everyone will be happy :)
> 
> Hehe, not really. See I am not happy :(

Why not?  Why does this have to be exported in debugfs?  Just delete it,
who cares about it?  It's just "debugging".

> So, what do you suggest? Should we create debugfs_create_ulong()?

Ick, do we _really_ need and want that?

> And how to implement that? With existing u32/u64 APIs or from scratch?

It's probably easy to just do in a few lines "from scratch", if you
really need/want it, right?

thanks,

greg k-h

  reply	other threads:[~2015-10-07 17:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07  7:35 [PATCH] PM / OPP: fix debugfs files for 64-bit Arnd Bergmann
2015-10-07 10:59 ` Viresh Kumar
2015-10-07 11:03   ` Viresh Kumar
2015-10-07 11:07     ` Greg Kroah-Hartman
2015-10-07 11:21       ` Viresh Kumar
2015-10-07 12:57         ` Greg Kroah-Hartman
2015-10-07 13:03           ` Viresh Kumar
2015-10-07 17:19             ` Greg Kroah-Hartman
2015-10-07 17:27               ` Viresh Kumar
2015-10-07 17:39                 ` Greg Kroah-Hartman [this message]
2015-10-07 18:00                   ` Viresh Kumar
2015-10-07 19:12             ` Arnd Bergmann
2015-10-08  7:48               ` Viresh Kumar
2015-10-08 14:25                 ` Alan Stern
2015-10-19 15:40                 ` Michael Turquette
2015-10-19 15:53                   ` Russell King - ARM Linux
2015-10-20 10:22                     ` Michael Turquette
2015-10-07 16:33         ` Russell King - ARM Linux
2015-10-07 16:36           ` Viresh Kumar

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=20151007173934.GB10665@kroah.com \
    --to=gregkh@linuxfoundation$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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