From: <Conor.Dooley@microchip.com>
To: <atulkhare@rivosinc.com>
Cc: <palmer@rivosinc.com>, <linux-i2c@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<robh@kernel.org>
Subject: Re: [PATCH v2 0/2] dt-bindings: sifive: fix dt-schema errors
Date: Tue, 26 Jul 2022 16:42:40 +0000 [thread overview]
Message-ID: <dd128dec-6092-7aeb-6e66-eb45cea3b0cd@microchip.com> (raw)
In-Reply-To: <fb861221-2e9d-7d4a-dd52-b16b3b581fd6@microchip.com>
On 01/07/2022 21:00, Conor Dooley wrote:
> On 01/07/2022 20:49, Atul Khare wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> Conor,
>>
>> Apologies for the delay, but my laptop died a couple of weeks ago, and
>> I have been scrambling to get things up and running on the
>> replacement. I will try and get back to it ASAP.
>
> Nothing you can do about your laptop dying :)
>
>
Hey Atul,
Been another couple weeks so I am going to send a v3 of these
patches (although without any changes to the v2) and we can
resume discussion about the cache binding change there.
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-07-26 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 23:39 [PATCH v2 0/2] dt-bindings: sifive: fix dt-schema errors Atul Khare
2022-06-09 6:22 ` Conor.Dooley
2022-06-09 15:13 ` Rob Herring
2022-06-09 15:18 ` Conor.Dooley
2022-06-18 12:40 ` Conor.Dooley
2022-07-01 19:49 ` Atul Khare
2022-07-01 20:00 ` Conor.Dooley
2022-07-26 16:42 ` Conor.Dooley [this message]
2022-08-15 16:28 ` Atul Khare
2022-08-15 16:33 ` Conor.Dooley
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=dd128dec-6092-7aeb-6e66-eb45cea3b0cd@microchip.com \
--to=conor.dooley@microchip.com \
--cc=atulkhare@rivosinc.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=robh@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).