From: <Codrin.Ciubotariu@microchip.com>
To: <Conor.Dooley@microchip.com>, <peda@axentia.se>, <wsa@kernel.org>,
<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: Wed, 15 Jun 2022 08:34:09 +0000 [thread overview]
Message-ID: <0e7faa1d-a26e-d00a-9d66-a48a232d8bb6@microchip.com> (raw)
In-Reply-To: <c26cb513-9cd3-6e87-9345-21d57e5a207d@microchip.com>
On 14.06.2022 17:25, Conor Dooley - M52691 wrote:
> On 14/06/2022 14:53, Codrin.Ciubotariu@microchip.com wrote:
>> On 14.06.2022 11:25, Codrin Ciubotariu wrote:
>>> On 13.06.2022 18:43, Peter Rosin wrote:
>>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>>>> the content is safe
>>>>
>>>> Hi!
>>>>
>>>> 2022-06-13 at 16:58, Wolfram Sang wrote:
>>>>> 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]? :)
>>>
>>> I replied two times, but it looks like my e-mails also don't reach the
>>> list.
>>>
>>>>
>>>> I replied to patch 1/3 and 2/3 but have not seen them on the lists and
>>>> patchwork also appears to be in the dark.
>>>> Did the replies make it anywhere? Should I resend?
>>>
>>> Same in my case. I though it has something to do with my setup or
>>> Microchip's IT, but it looks like it's not the case.
>>>
>>> I can resend the patches. Hopefully it will help.
>>
>> I resent the patch-set, replied and the replies still don't appear.
>
> This one (and the other one mentioning IT) went through for me.
> Anything you're doing differently?
>
> I guess you can also always fall back to using send-email w/
> the command from the lore page if for w/e reason using tbird
> is failing for you?
These replies worked fine, but the replies to the patches didn't.
Best regards,
Codrin
next prev parent reply other threads:[~2022-06-15 8:34 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
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 [this message]
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=0e7faa1d-a26e-d00a-9d66-a48a232d8bb6@microchip.com \
--to=codrin.ciubotariu@microchip.com \
--cc=Conor.Dooley@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 \
--cc=wsa@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).