From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Juergen Gross <jgross@suse.com>
Cc: minios-devel@lists.xenproject.org,
xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com
Subject: Re: [PATCH] mini-os: replace lib/printf.c with a version not under GPL
Date: Sun, 3 Jul 2016 20:35:47 +0200 [thread overview]
Message-ID: <20160703183547.GG5041@var.home> (raw)
In-Reply-To: <1467365607-22499-1-git-send-email-jgross@suse.com>
Hello,
Juergen Gross, on Fri 01 Jul 2016 11:33:27 +0200, wrote:
> Instead of a Linux kernel based implementation use one from freeBSD.
That'd be useful indeed :)
> I'm not sure about coding style here: should I keep (more or less) the
> one from freeBSD, or is the Xen style preferred?
I'd say just keep the file as it is upstream, so we can sync more easily
in the future.
> diff --git a/include/lib-gpl.h b/include/lib-gpl.h
> index d5602b2..7557627 100644
> --- a/include/lib-gpl.h
> +++ b/include/lib-gpl.h
Please move the content to lib.h then, since it won't be gpl any more.
Did you check the boot output e.g. of a trivial mini-os application?
Notably, iirc there were perhaps odd formating with %x, %p or such.
Moving to the posix behavior would be a good thing, I'd just want to
know whether we have some behavior change.
Thanks,
Samuel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-03 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 9:33 [PATCH] mini-os: replace lib/printf.c with a version not under GPL Juergen Gross
2016-07-03 18:35 ` Samuel Thibault [this message]
2016-07-04 5:29 ` Juergen Gross
2016-07-04 19:26 ` Samuel Thibault
2016-07-12 8:00 ` [Minios-devel] " Wei Liu
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=20160703183547.GG5041@var.home \
--to=samuel.thibault@ens-lyon.org \
--cc=andrew.cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=minios-devel@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).