From: Jean Delvare <jdelvare@suse.de>
To: Angelo Compagnucci <angelo@amarulasolutions.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH 2/2] README: adding documentation for BUILD_DYNAMIC_LIB
Date: Wed, 6 Dec 2017 10:48:41 +0100 [thread overview]
Message-ID: <20171206104841.23949233@endymion> (raw)
In-Reply-To: <1512029547-8639-2-git-send-email-angelo@amarulasolutions.com>
On Thu, 30 Nov 2017 09:12:27 +0100, Angelo Compagnucci wrote:
> This patch adds the documentation for the newly introduced
> BUILD_DYNAMIC_LIB flag and clarify the use of the other
> variables USE_STATIC_LIB and BUILD_STATIC_LIB.
>
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> ---
> README | 9 +++++++++
> 1 file changed, 9 insertions(+)
> (...)
Applied with minor editions, thanks.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2017-12-06 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 8:12 [PATCH 1/2] Makefile: add flag to disable dynamic libraries Angelo Compagnucci
2017-11-30 8:12 ` [PATCH 2/2] README: adding documentation for BUILD_DYNAMIC_LIB Angelo Compagnucci
2017-12-06 9:48 ` Jean Delvare [this message]
2017-12-06 9:48 ` [PATCH 1/2] Makefile: add flag to disable dynamic libraries Jean Delvare
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=20171206104841.23949233@endymion \
--to=jdelvare@suse.de \
--cc=angelo@amarulasolutions.com \
--cc=linux-i2c@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).