From: Wolfram Sang <wsa@the-dreams.de>
To: rpjday@crashcourse.ca
Cc: linux-i2c@vger.kernel.org
Subject: Re: where to report i2c-related man page issues?
Date: Mon, 24 Jul 2017 19:41:45 +0200 [thread overview]
Message-ID: <20170724174145.GA1543@katana> (raw)
In-Reply-To: <20170724081734.Horde.FhzpnpyGm_BJDSG1hHxDRxI@crashcourse.ca>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Mon, Jul 24, 2017 at 08:17:34AM -0400, rpjday@crashcourse.ca wrote:
>
> where is the right place to point out current i2c man page issues,
> or out-of-date passages? thank you kindly.
If you mean i2c-tools, then let me quote the README:
QUESTIONS AND BUG REPORTS
-------------------------
Please post your questions and bug reports to the linux-i2c mailing list:
linux-i2c@vger.kernel.org
with Cc to the current maintainer:
Jean Delvare <jdelvare@suse.de>
For additional information about this list, see:
http://vger.kernel.org/vger-lists.html#linux-i2c
So, you found the right list, but missed a CC. Still assuming you are talking
about i2c-tools...
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-24 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 12:17 where to report i2c-related man page issues? rpjday
2017-07-24 17:41 ` Wolfram Sang [this message]
2017-07-24 18:16 ` Robert P. J. Day
2017-07-24 19:05 ` Robert P. J. Day
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=20170724174145.GA1543@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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