Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: "Jean Delvare" <jdelvare@suse.com>,
	"Stephen Horvath" <s.horvath@outlook.com.au>,
	"Brigham Campbell" <me@brighamcampbell.com>,
	"Benoît Monin" <benoit.monin@bootlin.com>
Subject: Re: [PATCH i2c-tools] TODO: add file and describe items for the 4.5 release
Date: Tue, 7 Jul 2026 13:51:28 +0200	[thread overview]
Message-ID: <akzoQNeHb24X-XlA@shikoro> (raw)
In-Reply-To: <20260705181043.3757-1-wsa+renesas@sang-engineering.com>

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

On Sun, Jul 05, 2026 at 08:10:42PM +0200, Wolfram Sang wrote:
> We need help, especially with tests, for the next release. To make this
> visible, document the planned items and explain where and how people can
> participate.
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

Guys, thank you! I just had a little hope that this text file might draw
some attention, but still wanted to try nonetheless. You exceeded my
expectations by far and already tackled most of the action items. Really
awesome! I will look at your contributions today. We probably don't need
this TODO file after all. Yay, happy!


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

      parent reply	other threads:[~2026-07-07 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 18:10 [PATCH i2c-tools] TODO: add file and describe items for the 4.5 release Wolfram Sang
2026-07-06  4:45 ` Brigham Campbell
2026-07-06  5:19   ` Stephen Horvath
2026-07-06  6:33     ` Brigham Campbell
2026-07-07 12:16       ` Wolfram Sang
2026-07-06  8:04 ` Benoît Monin
2026-07-07 11:51 ` Wolfram Sang [this message]

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=akzoQNeHb24X-XlA@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=benoit.monin@bootlin.com \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=s.horvath@outlook.com.au \
    /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