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: Mon, 15 Aug 2022 16:33:56 +0000 [thread overview] Message-ID: <7595dda7-66db-5db0-b74e-4802e56962f4@microchip.com> (raw) In-Reply-To: <CABMhjYrB+Qn9ZuJ3Lqpu0KVFGeg6avxkYqD=SQWyLjdQ3wSpjg@mail.gmail.com> On 15/08/2022 17:28, Atul Khare wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Conor, > > Thanks -- really appreciate the help. Dell had to come out twice to > fix my laptop, and it's finally done (hopefully), but moving back and > forth between the different distros has been really disruptive. Ye, no worries. Not sure if you saw or Palmer told you - but I resubmitted the GPIO patch & a revised version of the interrupts, so that all made it into v6.0-rc1 :) FWIW they are: 5cef38dd03f3 dt-bindings: gpio: sifive: add gpio-line-names b60cf8e59e61 dt-bindings: riscv: fix SiFive l2-cache's cache-sets I assume it ended up in your inbox but you weren't actually set up to reply properly. Thanks, Conor. > > > On Tue, Jul 26, 2022 at 9:42 AM <Conor.Dooley@microchip.com> wrote: >> >> 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.
WARNING: multiple messages have this Message-ID (diff)
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: Mon, 15 Aug 2022 16:33:56 +0000 [thread overview] Message-ID: <7595dda7-66db-5db0-b74e-4802e56962f4@microchip.com> (raw) In-Reply-To: <CABMhjYrB+Qn9ZuJ3Lqpu0KVFGeg6avxkYqD=SQWyLjdQ3wSpjg@mail.gmail.com> On 15/08/2022 17:28, Atul Khare wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Conor, > > Thanks -- really appreciate the help. Dell had to come out twice to > fix my laptop, and it's finally done (hopefully), but moving back and > forth between the different distros has been really disruptive. Ye, no worries. Not sure if you saw or Palmer told you - but I resubmitted the GPIO patch & a revised version of the interrupts, so that all made it into v6.0-rc1 :) FWIW they are: 5cef38dd03f3 dt-bindings: gpio: sifive: add gpio-line-names b60cf8e59e61 dt-bindings: riscv: fix SiFive l2-cache's cache-sets I assume it ended up in your inbox but you weren't actually set up to reply properly. Thanks, Conor. > > > On Tue, Jul 26, 2022 at 9:42 AM <Conor.Dooley@microchip.com> wrote: >> >> 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-08-15 16:34 UTC|newest] Thread overview: 20+ 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-08 23:39 ` Atul Khare 2022-06-09 6:22 ` Conor.Dooley 2022-06-09 6:22 ` Conor.Dooley 2022-06-09 15:13 ` Rob Herring 2022-06-09 15:13 ` Rob Herring 2022-06-09 15:18 ` Conor.Dooley 2022-06-09 15:18 ` Conor.Dooley 2022-06-18 12:40 ` Conor.Dooley 2022-06-18 12:40 ` Conor.Dooley 2022-07-01 19:49 ` Atul Khare 2022-07-01 19:49 ` Atul Khare 2022-07-01 20:00 ` Conor.Dooley 2022-07-01 20:00 ` Conor.Dooley 2022-07-26 16:42 ` Conor.Dooley 2022-07-26 16:42 ` Conor.Dooley 2022-08-15 16:28 ` Atul Khare 2022-08-15 16:28 ` Atul Khare 2022-08-15 16:33 ` Conor.Dooley [this message] 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=7595dda7-66db-5db0-b74e-4802e56962f4@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.