From: John Spencer <maillist-lvm@barfooze.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [PATCH] fix missing include directives
Date: Sun, 10 Feb 2013 00:18:06 +0100 [thread overview]
Message-ID: <5116D92E.7040107@barfooze.de> (raw)
In-Reply-To: <510D3B57.3020607@barfooze.de>
On 02/02/2013 05:14 PM, John Spencer wrote:
> on glibc, those are erroneously (namespace pollution) pulled in via
> other headers. this doesn't work with conformant libcs (musl libc in
> this case), we simply need to include all needed headers.
>
> Signed-Off-By: John Spencer <maillist-lvm@barfooze.de>
>
>
ping
next prev parent reply other threads:[~2013-02-09 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 16:14 [linux-lvm] [PATCH] fix missing include directives John Spencer
2013-02-09 23:18 ` John Spencer [this message]
2013-02-21 13:42 ` John Spencer
2013-02-21 16:54 ` Zdenek Kabelac
2013-02-21 16:55 ` Zdenek Kabelac
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=5116D92E.7040107@barfooze.de \
--to=maillist-lvm@barfooze.de \
--cc=linux-lvm@redhat.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 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).