From: Wolfram Sang <wsa@kernel.org>
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: zev@bewilderbeest.net, robh+dt@kernel.org, davem@davemloft.net,
kuba@kernel.org, brendanhiggins@google.com,
benh@kernel.crashing.org, joel@jms.id.au, andrew@aj.id.au,
avifishman70@gmail.com, tmaimon77@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, jk@codeconstruct.com.au,
linux-i2c@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/6] MCTP I2C driver
Date: Mon, 29 Nov 2021 20:34:44 +0100 [thread overview]
Message-ID: <YaUrVD0AMwCc7+Cf@kunai> (raw)
In-Reply-To: <20211124031522.GB18900@codeconstruct.com.au>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
Hi Matt,
sorry for the long delay. This cycle, I am concentrating on overhauling the
bus_recovery handling. I am rather unsure if I have the bandwidth for
larger block reads this cycle. But it is planned for next cycle.
> > (extending SMBus calls to 255 byte) is complicated because we need ABI
> > backwards compatibility.
>
> Is it only the i2c-dev ABI that you are concerned about?
To at least give you a pointer what we discussed last time, have a look
here:
https://lore.kernel.org/r/20200728004708.4430-1-daniel.stodden@gmail.com
I can't go into details now because they escaped my mind :/ But I'll
work into it again when the bus_recovery thing is done and the recent
driver patches are handled. But you probably will get the idea without
me...
Thanks for sharing your script and working on the issue.
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-11-29 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 2:49 [PATCH net-next v3 0/6] MCTP I2C driver Matt Johnston
2021-11-15 2:49 ` [PATCH net-next v3 1/6] i2c: core: Allow 255 byte transfers for SMBus 3.x Matt Johnston
2021-11-15 2:49 ` [PATCH net-next v3 2/6] i2c: dev: Handle 255 byte blocks for i2c ioctl Matt Johnston
2021-11-15 2:49 ` [PATCH net-next v3 3/6] i2c: aspeed: Allow 255 byte block transfers Matt Johnston
2021-11-15 2:49 ` [PATCH net-next v3 4/6] i2c: npcm7xx: Allow 255 byte block SMBus transfers Matt Johnston
2021-11-15 2:49 ` [PATCH net-next v3 5/6] dt-bindings: net: New binding mctp-i2c-controller Matt Johnston
2021-11-15 2:49 ` [PATCH net-next v3 6/6] mctp i2c: MCTP I2C binding driver Matt Johnston
2021-11-15 14:20 ` [PATCH net-next v3 0/6] MCTP I2C driver patchwork-bot+netdevbpf
2021-11-15 15:30 ` Wolfram Sang
2021-11-15 16:08 ` Jakub Kicinski
2021-11-15 16:11 ` Wolfram Sang
2021-11-24 3:15 ` Matt Johnston
2021-11-29 19:34 ` 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=YaUrVD0AMwCc7+Cf@kunai \
--to=wsa@kernel.org \
--cc=andrew@aj.id.au \
--cc=avifishman70@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=benjaminfair@google.com \
--cc=brendanhiggins@google.com \
--cc=davem@davemloft.net \
--cc=jk@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.com \
--cc=zev@bewilderbeest.net \
/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).