[PATCH i2c-tools] README: ask for DCO in contributions

[PATCH i2c-tools] README: ask for DCO in contributions

[Wolfram Sang]

Add some documentation we can point contributors to wrt. DCO.

Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
 README | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/README b/README
index fb7bd03..98b4ae4 100644
--- a/README
+++ b/README
@@ -106,3 +106,11 @@ 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
+
+CONTRIBUTIONS
+-------------
+
+Contributions are very welcome. Please send them to the linux-i2x mailing list
+mentioned above. Make sure they include a 'Developer's certificate of origin'
+as used for the Linux Kernel and described here:
+  https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
-- 
2.43.0

Re: [PATCH i2c-tools] README: ask for DCO in contributions

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 206 bytes --]

> +Contributions are very welcome. Please send them to the linux-i2x mailing list

Argh, who put an 'x' there to make it i2x??

Anyhow, this is still a call for opinions on requesting DCO for
i2c-tools...


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]