public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <robh@kernel.org>, <atulkhare@rivosinc.com>, <palmer@rivosinc.com>
Cc: <Conor.Dooley@microchip.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>
Subject: Re: [PATCH v2 0/2] dt-bindings: sifive: fix dt-schema errors
Date: Thu, 9 Jun 2022 15:18:31 +0000	[thread overview]
Message-ID: <57776fa5-4eaf-7074-9bc1-5401da637980@microchip.com> (raw)
In-Reply-To: <20220609151353.GA3805719-robh@kernel.org>

On 09/06/2022 16:13, Rob Herring wrote:
> On Wed, Jun 08, 2022 at 04:39:23PM -0700, Atul Khare wrote:
>> The patch series fixes dt-schema validation errors that can be reproduced
>> using the following: make ARCH=riscv defconfig; make ARCH=riscv
>> dt_binding_check dtbs_check
>>
>> This is a rebased version of https://tinyurl.com/yvdvmsjd, and excludes
>> two patches that are now redundant.
>>
>> Atul Khare (2):
>>   dt-bindings: sifive: add cache-set value of 2048
>>   dt-bindings: sifive: add gpio-line-names
> 
> Your series is not properly threaded. git-send-email does this for you 
> by default unless you tell it not to.

Aye, v1 was the same.
@Palmer could you please give Atul a hand w/ mail client/send email
things?

Thanks,
Conor.

> 
>>
>>  Documentation/devicetree/bindings/gpio/sifive,gpio.yaml      | 3 +++
>>  Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 4 +++-
>>  2 files changed, 6 insertions(+), 1 deletion(-)
>>
>> --
>> 2.34.1
>>
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-06-09 15:18 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 [this message]
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
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=57776fa5-4eaf-7074-9bc1-5401da637980@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