From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH i2c-tools v2] README: ask for DCO in contributions
Date: Thu, 8 Aug 2024 11:28:01 +0200 [thread overview]
Message-ID: <20240808112746.42fa8590@endymion.delvare> (raw)
In-Reply-To: <20240807112835.14346-1-wsa+renesas@sang-engineering.com>
Hi Wolfram,
On Wed, 7 Aug 2024 13:24:33 +0200, Wolfram Sang wrote:
> Add some documentation we can point contributors to wrt. DCO.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> Change since v1:
> * s/i2x/i2c/
>
> @Jean: do you agree to asking for DCOs in i2c-tools? Also, together with
Yes, fine with me.
> the 'i2ctransfer' improvements I just sent out, I think we could aim for
> a 4.4 release soon, or? It's been 3 years and the updates are small but
> still neat, I think.
OK!
>
>
> README | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/README b/README
> index fb7bd03..2d342e5 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-i2c 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
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2024-08-08 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 11:24 [PATCH i2c-tools v2] README: ask for DCO in contributions Wolfram Sang
2024-08-08 9:28 ` Jean Delvare [this message]
2024-08-14 18:09 ` Wolfram Sang
2024-09-12 12:42 ` Jean Delvare
2024-09-12 18:46 ` Wolfram Sang
2024-08-10 21:40 ` Wolfram Sang
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=20240808112746.42fa8590@endymion.delvare \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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