From: Wolfram Sang <wsa@kernel.org>
To: Daniel Stodden <daniel.stodden@gmail.com>
Cc: linux-i2c@vger.kernel.org, jdelvare@suse.de
Subject: Re: [RFC PATCH v2] i2c: Support Smbus 3.0 block sizes up to 255 bytes.
Date: Fri, 8 Jan 2021 14:11:47 +0100 [thread overview]
Message-ID: <20210108131147.GA1023@ninjato> (raw)
In-Reply-To: <78317552-E485-46B4-84EA-625E6E0CBF54@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
Hi Daniel,
thanks for your response!
> Don’t be, I’m sorry. This came out of a SONiC-related project at work. Work
> got fixed and moved on. I was originally going to keep this an upstream project
> after hours, then fell off the rails.
I understand, happened to me as well. Is it okay to CC you on patches?
Or are you too far away from it meanwhile?
> As for v2 — I still believe the direction is good. The main issue I
> had was that I lacked insight into one or more popular-enough
> commodity bus drivers (amd? nvidia? intel?), for further verification,
> as opposed to our proprietary accels around here.
Real HW setups for testing are a problem, yes. I noticed this, too, when
I said I fix the existing drivers. I reconsidered. Fixing them would
result in non-trivial changes which need testing SMBUS_BLOCK_DATA
transfers. This is too rare, so I'll just focus on the systems I have at
hand. Digging in deeper, I found there is enough to fix at the core
level anyhow. I won't be bored.
> That 1->2 succession you outline below, starting with kernel and kernel-clients,
> sounds a lot like what I was missing.
Yeah, I hope it grows the pool of interested people.
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-08 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 20:36 [RFC PATCH v2] i2c: Support Smbus 3.0 block sizes up to 255 bytes daniel.stodden
2021-01-06 15:27 ` Wolfram Sang
2021-01-06 18:13 ` Daniel Stodden
2021-01-08 13:11 ` 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=20210108131147.GA1023@ninjato \
--to=wsa@kernel.org \
--cc=daniel.stodden@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).