All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Philipson <ross.philipson@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Zhang, Eniac" <eniac-xw.zhang@hp.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: passing smbios table from qemu
Date: Tue, 14 Jan 2014 10:39:19 -0500	[thread overview]
Message-ID: <52D55A27.4090103@citrix.com> (raw)
In-Reply-To: <1389713030.12434.86.camel@kazak.uk.xensource.com>

On 01/14/2014 10:23 AM, Ian Campbell wrote:
> On Tue, 2014-01-14 at 10:21 -0500, Ross Philipson wrote:
>> On 01/13/2014 06:31 AM, Ian Jackson wrote:
>>> Ian Campbell writes ("Re: [Xen-devel] passing smbios table from qemu"):
>>>> On Fri, 2014-01-10 at 15:32 -0500, Ross Philipson wrote:
>>>>> On 01/10/2014 10:03 AM, Ian Campbell wrote:
>>>>>> Fitting in with libxl proper would require the API to look a certain way
>>>>>> (take a context etc), so perhaps libxlu would be more appropriate,
>>>>>> alongside the disk syntax parser etc?
>>>>>
>>>>> Possibly. I looked at that back then (and today again) and it seemed to
>>>>> all be related to parsing things into XLU_Config objects. I guess I did
>>>>> not have a good feel for what libxlu was supposed to be. If it is
>>>>> supposed to be a generic library of auxiliary toolstack functionality
>>>>> then I think it would be a good place.
>>>>
>>>> I think that (aux functionality) was the intention -- the fact that it
>>>> is all parsing stuff right now is just a coincidence.
>>
>> Ok then libxlu sounds like a reasonable place for this. I will submit a
>> patch.
>
> Thanks. It's probably a bit late to squeeze this in for 4.4, so you've
> got a little while until 4.5 development opens.

Right, I will shoot for 4.5 then - thanks.

>
> Ian.
>
>


-- 
Ross Philipson

      reply	other threads:[~2014-01-14 15:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 21:01 passing smbios table from qemu Zhang, Eniac
2014-01-07 13:56 ` Ian Campbell
     [not found]   ` <3B22ECA2D19A3D408C83F4F15A9CB7D45076233C@G4W3221.americas.hpqcorp.net>
     [not found]     ` <DF407A7CCC374747A5BE5B7739FDEB181EFEE57D@G2W2433.americas.hpqcorp.net>
     [not found]       ` <3B22ECA2D19A3D408C83F4F15A9CB7D450762410@G4W3221.americas.hpqcorp.net>
     [not found]         ` <DF407A7CCC374747A5BE5B7739FDEB181EFEE61D@G2W2433.americas.hpqcorp.net>
     [not found]           ` <2559B97E2BCECA4BA2AF63DA8CF5C7200D095CD7@G1W3640.americas.hpqcorp.net>
2014-01-08 16:58             ` Zhang, Eniac
2014-01-08 17:51               ` Ian Campbell
2014-01-08 18:29   ` Ross Philipson
2014-01-09 10:06     ` Ian Campbell
2014-01-09 14:46       ` Ross Philipson
2014-01-09 14:56         ` Ian Campbell
2014-01-09 19:00         ` Konrad Rzeszutek Wilk
2014-01-10 10:20           ` Ian Campbell
2014-01-10 14:25             ` Ross Philipson
2014-01-10 15:03               ` Ian Campbell
2014-01-10 20:32                 ` Ross Philipson
2014-01-13 10:25                   ` Ian Campbell
2014-01-13 11:31                     ` Ian Jackson
2014-01-14 15:21                       ` Ross Philipson
2014-01-14 15:23                         ` Ian Campbell
2014-01-14 15:39                           ` Ross Philipson [this message]

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=52D55A27.4090103@citrix.com \
    --to=ross.philipson@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=eniac-xw.zhang@hp.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.