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: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Zhang, Eniac" <eniac-xw.zhang@hp.com>
Subject: Re: passing smbios table from qemu
Date: Fri, 10 Jan 2014 09:25:26 -0500	[thread overview]
Message-ID: <52D002D6.7090306@citrix.com> (raw)
In-Reply-To: <1389349212.19142.21.camel@kazak.uk.xensource.com>

On 01/10/2014 05:20 AM, Ian Campbell wrote:
> On Thu, 2014-01-09 at 14:00 -0500, Konrad Rzeszutek Wilk wrote:
>> On Thu, Jan 09, 2014 at 09:46:59AM -0500, Ross Philipson wrote:
>
>>> Your memory is intact; I did provide a helper library. I posted it
>>> as a tarball since I could not figure out where such a thing might
>>> live in the xen tree. I posted it twice - the second time with some
>>> fixes:
>>>
>>> http://lists.xen.org/archives/html/xen-devel/2013-03/msg01850.html
>>
>> Would it make sense to try to have it as part of the Xen tree?
>> It looks in good shape.
>
> I think we considered this before, but I can't remember why we didn't
> (assuming we even explicitly decided that rather than just letting it
> slip through the cracks).

It has been a while but yea, we did discuss putting it in the tools 
somewhere. I then went off and tried to find a reasonable place for it 
and could not. The last thing that happened was that I sent an email 
asking for suggestions, did not get any replies and then I got 
distracted (sorry 'bout that).

So I guess that is the question: where to put it? Should it be merged 
into another lib or be brought in as a separate lib or utility?

Thanks
Ross

>
> Ian.
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3658/6989 - Release Date: 01/09/14
>

  reply	other threads:[~2014-01-10 14:25 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 [this message]
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

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=52D002D6.7090306@citrix.com \
    --to=ross.philipson@citrix.com \
    --cc=Ian.Campbell@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.