From: Dario Faggioli <raistlin@linux.it>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
George Dunlap <dunlapg@gmail.com>,
Keir Fraser <keir.xen@gmail.com>, Jan Beulich <JBeulich@suse.com>
Subject: about libxc/ia64/
Date: Thu, 26 Jul 2012 19:44:32 +0200 [thread overview]
Message-ID: <1343324672.6187.61.camel@Solace> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 978 bytes --]
Hello,
Just out of curiosity, IIRC we killed ia64, right? If yes, is it fine
for this dir to be still there:
$ ls tools/libxc/ia64/
ac_ia64_tools.h Makefile xc_dom_ia64_util.c xc_ia64_dom_fwloader.c xc_ia64_hvm_build.c xc_ia64_linux_save.c xc_ia64_stubs.c
dom_fw_acpi.c sal.h xc_dom_ia64_util.h xc_ia64.h xc_ia64_linux_restore.c xc_ia64_save_restore.h
Again, just asking because these files are polluting my grep-s, and I
started wondering whether or not that is happening for a good reason.
If the question is stupid, just ignore it and forgive me. :-)
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-07-26 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 17:44 Dario Faggioli [this message]
2012-07-27 6:59 ` about libxc/ia64/ Ian Campbell
2012-07-27 7:12 ` Jan Beulich
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=1343324672.6187.61.camel@Solace \
--to=raistlin@linux.it \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dunlapg@gmail.com \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.