From: aq <aquynh@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH] fix broken ACM
Date: Fri, 24 Jun 2005 07:06:10 +0900 [thread overview]
Message-ID: <9cde8bff05062315067b7a7137@mail.gmail.com> (raw)
In-Reply-To: <6b08ec7c5c15235c3fb974971b1638ac@cl.cam.ac.uk>
On 6/24/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 23 Jun 2005, at 16:22, aq wrote:
>
> > Keir, certainly i understand your point. but this patch doesnt harm,
> > anyway ;-)
>
> We need to understand why a patch is useful before we apply it.
>
> > one annoying problem at the moment is that if we want to compile ACM
> > in, we should modify the value of ACM_USE_SECURITY_POLICY, since the
> > current default value is ACM_NULL_POLICY( which is meaningless as Keir
> > pointed out )
> >
> > any clean way to overcome this problem?
>
> The way I skip building acm directory in the root Makefile is quite
> gross, and won't actually detect if you edit ACM_USE_SECURITY_POLICY.
> Probably need to think about ways of cleanly expressing a new build
> config option for security policies etc. Then Makefile decision can
> hook off of that.
There is one solution: define the value of ACM_USE_SECURITY_POLICY in
xen/Makefile, then "make" will put its value into acm code (using sed
on a "template" configuration header file, for example)
Is that clean enough? If that is fine, I am ready to send a patch.
regards,
aq
next prev parent reply other threads:[~2005-06-23 22:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 17:40 [PATCH] fix broken ACM aq
2005-06-22 17:51 ` Keir Fraser
2005-06-22 17:52 ` aq
2005-06-23 7:48 ` Keir Fraser
2005-06-23 8:04 ` aq
2005-06-23 8:14 ` Keir Fraser
2005-06-23 8:19 ` aq
2005-06-22 18:22 ` aq
2005-06-23 3:42 ` Stefan Berger
2005-06-23 3:56 ` aq
2005-06-23 4:18 ` Stefan Berger
2005-06-23 7:56 ` aq
2005-06-23 14:57 ` Stefan Berger
2005-06-23 15:16 ` Keir Fraser
2005-06-23 15:22 ` aq
2005-06-23 15:52 ` Keir Fraser
2005-06-23 22:06 ` aq [this message]
2005-06-23 15:56 ` Stefan Berger
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=9cde8bff05062315067b7a7137@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=stefanb@us.ibm.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.