From: Fam Zheng <famz@redhat.com>
To: Eduardo Otubo <otubo@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] buildsys: Move seccomp cflags/libs to per object
Date: Fri, 8 Sep 2017 16:16:33 +0800 [thread overview]
Message-ID: <20170908081633.GH4511@lemon> (raw)
In-Reply-To: <20170908081057.GB16888@vader>
On Fri, 09/08 10:10, Eduardo Otubo wrote:
> On Thu, Sep 07, 2017 at 04:53:16PM +0800, Fam Zheng wrote:
> > Like many other libraries, libseccomp cflags and libs should only apply
> > to the building of necessary objects. Do so in the usual way with the
> > help of per object variables.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
>
> I'll include in the next pull request. Thanks for the patch.
Great, thanks!
Fam
prev parent reply other threads:[~2017-09-08 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 8:53 [Qemu-devel] [PATCH] buildsys: Move seccomp cflags/libs to per object Fam Zheng
2017-09-07 17:52 ` Philippe Mathieu-Daudé
2017-09-08 8:10 ` Eduardo Otubo
2017-09-08 8:16 ` Fam Zheng [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=20170908081633.GH4511@lemon \
--to=famz@redhat.com \
--cc=otubo@redhat.com \
--cc=qemu-devel@nongnu.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).