From: Rusty Russell <rusty@rustcorp.com.au>
To: Borislav Petkov <bp@alien8.de>, LKML <linux-kernel@vger.kernel.org>
Cc: Borislav Petkov <bp@suse.de>,
Sasha Levin <sasha.levin@oracle.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] tools: Unify export.h
Date: Tue, 25 Feb 2014 12:09:23 +1030 [thread overview]
Message-ID: <87eh2s55tg.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1393153753-2369-1-git-send-email-bp@alien8.de>
Borislav Petkov <bp@alien8.de> writes:
> From: Borislav Petkov <bp@suse.de>
>
> So tools/ has been growing three, at a different stage of their
> development export.h headers and so we should unite into one. Add
> tools/include/ to the include path of virtio and liblockdep to pick the
> shared header now.
Should we get more ambitious and start a fake-kernel/ directory where
we can put userspace equivs/stubs of kernel functionality?
Cheers,
Rusty.
next prev parent reply other threads:[~2014-02-25 5:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 11:09 [PATCH] tools: Unify export.h Borislav Petkov
2014-02-25 1:39 ` Rusty Russell [this message]
2014-02-25 7:00 ` Borislav Petkov
2014-02-25 12:22 ` Rusty Russell
2014-02-25 14:05 ` Arnaldo Carvalho de Melo
2014-04-10 17:38 ` Borislav Petkov
2014-04-11 11:59 ` Jiri Olsa
2014-04-12 10:14 ` Borislav Petkov
2014-04-13 11:27 ` [PATCH] tools: Consolidate types.h Borislav Petkov
2014-04-14 11:18 ` Jiri Olsa
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=87eh2s55tg.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=paulus@samba.org \
--cc=sasha.levin@oracle.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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