From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Robert P. J. Day" Subject: Re: where to report i2c-related man page issues? Date: Mon, 24 Jul 2017 15:05:57 -0400 (EDT) Message-ID: References: <20170724081734.Horde.FhzpnpyGm_BJDSG1hHxDRxI@crashcourse.ca> <20170724174145.GA1543@katana> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Received: from cpanel2.indieserve.net ([199.212.143.6]:56767 "EHLO cpanel2.indieserve.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752785AbdGXTGC (ORCPT ); Mon, 24 Jul 2017 15:06:02 -0400 In-Reply-To: <20170724174145.GA1543@katana> Sender: linux-i2c-owner@vger.kernel.org List-Id: linux-i2c@vger.kernel.org To: Wolfram Sang Cc: linux-i2c@vger.kernel.org On Mon, 24 Jul 2017, Wolfram Sang wrote: > 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 > For additional information about this list, see: > http://vger.kernel.org/vger-lists.html#linux-i2c by the way, the current README file does not include that "Cc" line. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================