On 06/14/2010 12:59 PM, john cooper wrote:
Anthony Liguori wrote:
On 06/09/2010 03:05 AM, john cooper wrote:
This patch adds the ability to determine the build-configured
runtime "config file" paths from the command line. After
support for cpu model definitions were added to the defa
Anthony Liguori wrote:
> On 06/09/2010 03:05 AM, john cooper wrote:
>> This patch adds the ability to determine the build-configured
>> runtime "config file" paths from the command line. After
>> support for cpu model definitions were added to the default
>> runtime "target-" config file, testing
On Mon, Jun 14, 2010 at 12:01:42PM -0500, Anthony Liguori wrote:
> On 06/09/2010 03:05 AM, john cooper wrote:
> >This patch adds the ability to determine the build-configured
> >runtime "config file" paths from the command line. After
> >support for cpu model definitions were added to the default
On 06/09/2010 03:05 AM, john cooper wrote:
This patch adds the ability to determine the build-configured
runtime "config file" paths from the command line. After
support for cpu model definitions were added to the default
runtime "target-" config file, testing of this feature has
tripped over an
This patch adds the ability to determine the build-configured
runtime "config file" paths from the command line. After
support for cpu model definitions were added to the default
runtime "target-" config file, testing of this feature has
tripped over an unintentionally mis-installed config file
en
