public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: "Li, Aubrey" <aubrey.li@linux.intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	mingo@redhat.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org,
	"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: [PATCH] x86: new Intel Atom SoC power management controller driver
Date: Thu, 06 Mar 2014 08:30:54 -0800	[thread overview]
Message-ID: <5318A2BE.2070707@linux.intel.com> (raw)
In-Reply-To: <53180E98.9000608@linux.intel.com>

On 03/05/2014 09:58 PM, Li, Aubrey wrote:
>>
>> What we absolutely don't want to happen is someone starting to use these
>> unstable interfaces for something other than debugging.  If debugfs ever
>> needs to be mounted in a system for full functionality, that is a bug.
> 
> Understood. But we don't have a plan to use it now. Just for observation
> and diagnosis purpose only.
> 
> Are you suggesting we should put them into sysfs now?
> 

No, I'm just trying to understand if there is a risk.

	-hpa



  reply	other threads:[~2014-03-06 16:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  3:31 [PATCH] x86: new Intel Atom SoC power management controller driver Li, Aubrey
2014-03-06  3:49 ` H. Peter Anvin
2014-03-06  5:21   ` Li, Aubrey
2014-03-06  5:28     ` H. Peter Anvin
2014-03-06  5:33       ` Li, Aubrey
2014-03-06  5:52         ` H. Peter Anvin
2014-03-06  5:58           ` Li, Aubrey
2014-03-06 16:30             ` H. Peter Anvin [this message]
2014-03-07  0:26               ` Li, Aubrey
2014-03-07  0:41                 ` Joe Perches
2014-03-07  2:08                   ` Li, Aubrey
2014-03-07  2:21                     ` Joe Perches
2014-03-07  3:04                       ` Li, Aubrey

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=5318A2BE.2070707@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=alan@linux.intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mjg59@srcf.ucam.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