diff options
| author | Wolfram Sang <wsa+renesas@sang-engineering.com> | 2020-08-06 16:15:06 +0200 |
|---|---|---|
| committer | Wolfram Sang <wsa@kernel.org> | 2020-08-10 12:06:19 +0200 |
| commit | 14281056546e45230384e1f0ecf8ec59703a5b26 (patch) | |
| tree | 4809b4c3ad279b55f0dbdba3d9b4134385b406c2 /tools | |
| parent | 162ed6c94528d743ee94cfd209a2e866c4f7d77a (diff) | |
| download | i2c-tools-git-14281056546e45230384e1f0ecf8ec59703a5b26.tar.gz | |
add BUGS section to manpages
For all manpages installed on my Debian system, add a BUGS section, so
people can easily find whom to contact.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/i2cdetect.8 | 4 | ||||
| -rw-r--r-- | tools/i2cdump.8 | 4 | ||||
| -rw-r--r-- | tools/i2cget.8 | 4 | ||||
| -rw-r--r-- | tools/i2cset.8 | 4 | ||||
| -rw-r--r-- | tools/i2ctransfer.8 | 4 |
5 files changed, 20 insertions, 0 deletions
diff --git a/tools/i2cdetect.8 b/tools/i2cdetect.8 index 14c1f18..9e9f7cc 100644 --- a/tools/i2cdetect.8 +++ b/tools/i2cdetect.8 @@ -113,6 +113,10 @@ using the "receive byte" method, after user confirmation: .RE .fi +.SH BUGS +To report bugs or send fixes, please write to the Linux I2C mailing list +<linux-i2c@vger.kernel.org>. + .SH SEE ALSO i2cdump(8), i2cget(8), i2cset(8), i2ctransfer(8), sensors-detect(8) diff --git a/tools/i2cdump.8 b/tools/i2cdump.8 index 18bf600..6acfcc2 100644 --- a/tools/i2cdump.8 +++ b/tools/i2cdump.8 @@ -116,6 +116,10 @@ user confirmation: .RE .fi +.SH BUGS +To report bugs or send fixes, please write to the Linux I2C mailing list +<linux-i2c@vger.kernel.org>. + .SH SEE ALSO i2cdetect(8), i2cget(8), i2cset(8), i2ctransfer(8), isadump(8) diff --git a/tools/i2cget.8 b/tools/i2cget.8 index 680279f..ac4024a 100644 --- a/tools/i2cget.8 +++ b/tools/i2cget.8 @@ -113,6 +113,10 @@ equivalent, so this is the only way to read data from a large EEPROM if your master isn't fully I2C capable. With a fully I2C capable master, you would use \fIi2ctransfer\fR to achieve the same in a safe and faster way. +.SH BUGS +To report bugs or send fixes, please write to the Linux I2C mailing list +<linux-i2c@vger.kernel.org>. + .SH SEE ALSO i2cdetect(8), i2cdump(8), i2cset(8), i2ctransfer(8) diff --git a/tools/i2cset.8 b/tools/i2cset.8 index 8c73c60..138f545 100644 --- a/tools/i2cset.8 +++ b/tools/i2cset.8 @@ -125,6 +125,10 @@ address 0x48 on bus 1 (i2c-1), after user confirmation: Also see i2cget(8) for examples of combined usage of \fIi2cset\fR and \fIi2cget\fR. +.SH BUGS +To report bugs or send fixes, please write to the Linux I2C mailing list +<linux-i2c@vger.kernel.org>. + .SH SEE ALSO i2cdetect(8), i2cdump(8), i2cget(8), i2ctransfer(8), isaset(8) diff --git a/tools/i2ctransfer.8 b/tools/i2ctransfer.8 index d16e34e..cf2d14c 100644 --- a/tools/i2ctransfer.8 +++ b/tools/i2ctransfer.8 @@ -151,6 +151,10 @@ It can confuse your I2C bus, cause data loss, or have more serious side effects. Writing to a serial EEPROM on a memory DIMM (chip addresses between 0x50 and 0x57) may DESTROY your memory, leaving your system unbootable! Be extremely careful using this program. +.SH BUGS +To report bugs or send fixes, please write to the Linux I2C mailing list +<linux-i2c@vger.kernel.org>. + .SH AUTHORS Wolfram Sang, based on .B i2cget |