From: David Howells <dhowells@redhat.com>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH 0/4] keyutils: fix compilation error with C++
Date: Mon, 06 Jul 2020 20:27:55 +0000 [thread overview]
Message-ID: <2973696.1594067275@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200702085723.7026-1-cvubrugier@fastmail.fm>
Christophe Vu-Brugier <cvubrugier@fastmail.fm> wrote:
> * Patch #1 fixes a few typos in the man pages.
> * Patch #2 fixes the aforementioned issue.
> * Patch #3 helps prevent a similar issue from happening in the future.
> * Patch #4 fixes an issue reported by C++ compilers at link time.
Applied.
David
prev parent reply other threads:[~2020-07-06 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 8:57 [PATCH 0/4] keyutils: fix compilation error with C++ Christophe Vu-Brugier
2020-07-02 8:57 ` [PATCH 1/4] man: fix typos Christophe Vu-Brugier
2020-07-02 8:57 ` [PATCH 2/4] Fix compilation error when keyutils.h is used in C++ Christophe Vu-Brugier
2020-07-02 8:57 ` [PATCH 3/4] Check that keyutils.h has valid C++ syntax at build time Christophe Vu-Brugier
2020-07-02 8:57 ` [PATCH 4/4] Fix error when a C++ program is linked with libkeyutils Christophe Vu-Brugier
2020-07-06 20:27 ` David Howells [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=2973696.1594067275@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=keyrings@vger.kernel.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).