From: Wolfram Sang <wsa@kernel.org>
To: Codrin.Ciubotariu@microchip.com
Cc: peda@axentia.se, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Ludovic.Desroches@microchip.com, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com, robh+dt@kernel.org,
kamel.bouhara@bootlin.com
Subject: Re: Regression: at24 eeprom writing times out on sama5d3
Date: Mon, 13 Jun 2022 16:58:40 +0200 [thread overview]
Message-ID: <YqdQoJbsgwjQ9PYh@shikoro> (raw)
In-Reply-To: <2bb4868b-90ab-887e-bf13-9de8b79231bd@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
Hi Codrin,
> could you please apply this patch-set [1] and let us know if it
> addresses your issue?
Any comments to the comments I gave to [1]? :)
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-13 18:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 14:28 Regression: at24 eeprom writing times out on sama5d3 Peter Rosin
2022-06-10 7:35 ` Codrin.Ciubotariu
2022-06-10 20:51 ` Peter Rosin
2022-06-30 7:44 ` Peter Rosin
2022-09-08 12:06 ` Thorsten Leemhuis
2022-09-08 13:59 ` Peter Rosin
2022-09-26 13:32 ` Regression: at24 eeprom writing times out on sama5d3 #forregzbot Thorsten Leemhuis
2022-12-15 17:53 ` Regression: at24 eeprom writing times out on sama5d3 Thorsten Leemhuis
2022-12-15 18:50 ` Conor.Dooley
2023-03-15 11:07 ` Linux regression tracking (Thorsten Leemhuis)
2022-06-13 14:58 ` Wolfram Sang [this message]
2022-06-13 15:43 ` Peter Rosin
2022-06-13 20:06 ` Wolfram Sang
2022-06-14 8:25 ` Codrin.Ciubotariu
2022-06-14 13:53 ` Codrin.Ciubotariu
2022-06-14 14:25 ` Conor.Dooley
2022-06-15 8:34 ` Codrin.Ciubotariu
2022-06-11 13:41 ` Thorsten Leemhuis
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=YqdQoJbsgwjQ9PYh@shikoro \
--to=wsa@kernel.org \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=kamel.bouhara@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@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