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>

CHANGES

@@ -2,6 +2,7 @@ i2c-tools CHANGES
 -----------------
 
 master
+  manpages: add BUGS section to let people know how to contact us
   Makefile: allow to preset all CFLAGS and LDFLAGS variables
   tools: Consistently use snprintf instead of sprintf
          Restrict addresses 0x03-0x07, too (defined by I2C standard)

eeprom/decode-dimms.1

@@ -62,6 +62,9 @@ Same as -x except treat multibyte hex data as little endian
 .TP
 .B \-h, --help
 Display the usage summary
+.SH BUGS
+To report bugs or send fixes, please write to the Linux I2C mailing list
+<linux-i2c@vger.kernel.org>.
 .SH SEE ALSO
 .BR decode-vaio (1)
 .SH AUTHORS

eeprom/decode-vaio.1

@@ -29,6 +29,9 @@ The purpose of the
 tool is to decode the information found in the Sony Vaio laptop
 identification EEPROMs.
 The tool requires the eeprom kernel module to be loaded.
+.SH BUGS
+To report bugs or send fixes, please write to the Linux I2C mailing list
+<linux-i2c@vger.kernel.org>.
 .SH SEE ALSO
 .BR decode-dimms (1)
 .SH AUTHOR

stub/i2c-stub-from-dump.8

@@ -45,6 +45,10 @@ There are some limitations to the kind of devices that can be handled:
 .IP \(bu
 Device must not have banks (as most Winbond devices do).
 
+.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), i2cdetect(8), i2cset(8)
 

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)
 

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)
 

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)
 

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)
 

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