From: Wolfram Sang <wsa@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2] libi2c: Add a manual page to document the API
Date: Tue, 8 Sep 2020 08:52:19 +0200 [thread overview]
Message-ID: <20200908065219.GB5936@ninjato> (raw)
In-Reply-To: <20200903120927.482b6eae@endymion>
[-- Attachment #1: Type: text/plain, Size: 240 bytes --]
On Thu, Sep 03, 2020 at 12:09:27PM +0200, Jean Delvare wrote:
> It is good practice for a library to come with a complete API description.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
Didn't review it, but glad you made it!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-09-08 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 10:09 [PATCH v2] libi2c: Add a manual page to document the API Jean Delvare
2020-09-08 6:52 ` Wolfram Sang [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=20200908065219.GB5936@ninjato \
--to=wsa@kernel.org \
--cc=jdelvare@suse.de \
--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).