lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51FEAD39.2030909@linux.intel.com>
Date:	Sun, 04 Aug 2013 12:36:25 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
	linux-kernel@...r.kernel.org, "Brown, Len" <len.brown@...el.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [RFC v01 0/3] Power Capping Framework

On 8/2/2013 5:53 PM, Greg KH wrote:
>> I will post the one client driver, which is already using this
>> framework as this series.
>>> Ideally you will have more than one client driver submitted, as a
>>> "framework" for just one driver seems a bit odd, don't you think?
>> There are other groups and vendors interested in using this
>> framework. But they want to make sure that this
>> framework can go to upstream Linux. We will provide one client using
>> this framework at this time.
>> Do you think this is a problem?
>
> I would love to see the feedback from those groups and vendors as well,
> to ensure that they agree with this.  Ideally, they would sign off on
> the patches, and provide clients that work with the framework at the
> same time.  Otherwise, I just have to take your word for it :)

I suspect that in some ways Intel is a year or two ahead in this regard,
we'll see if others are willing to speak up yet ;-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ