All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Kavyasree.Kotagiri@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <robh@kernel.org>
Cc: <Claudiu.Beznea@microchip.com>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<Nicolas.Ferre@microchip.com>, <lee@kernel.org>,
	<robh+dt@kernel.org>, <Sergiu.Moga@microchip.com>
Subject: RE: [RESEND PATCH v9 1/3] dt-bindings: mfd: Convert atmel-flexcom to json-schema
Date: Tue, 13 Sep 2022 10:16:18 +0000	[thread overview]
Message-ID: <CO1PR11MB4865D623FA957BE718C7A75292479@CO1PR11MB4865.namprd11.prod.outlook.com> (raw)
In-Reply-To: <98ab5118-aa32-af20-a732-dcb5e362717b@linaro.org>

> On 13/09/2022 07:29, Kavyasree.Kotagiri@microchip.com wrote:
> >>>>> flexcom@fc018000: spi@400: Unevaluated properties are not allowed
> >>>> ('dma-
> >>>>> names', 'dmas' were unexpected)
> >>>>>         arch/arm/boot/dts/at91-kizbox3-hs.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d27_som1_ek.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d27_wlsom1_ek.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d2_icp.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d2_ptc_ek.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d2_xplained.dtb
> >>>>
> >>>> dma properties for spi node is already being covered by Sergiu in below
> >>>> patch:
> >>>> https://lore.kernel.org/lkml/b4625526-8f9b-ada8-f854-
> >>>> 751a48545576@linaro.org/
> >>>>
> >>> Hi Rob, Please let me know your comments.
> >>
> >> this means it cannot be currently tested. Are you sure that there are no
> >> warnings in all DTBs with your patches?
> >>
> > Yes, I ran dtbs_check. I don’t see any warnings.
> 
> Then the warning could be probably ignored (I assume it is really fixed
> when both patchsets land).
> 
Yes. You are right.

> 
> Best regards,
> Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: <Kavyasree.Kotagiri@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <robh@kernel.org>
Cc: devicetree@vger.kernel.org, lee@kernel.org,
	linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com,
	robh+dt@kernel.org, Sergiu.Moga@microchip.com,
	krzysztof.kozlowski+dt@linaro.org, Claudiu.Beznea@microchip.com,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [RESEND PATCH v9 1/3] dt-bindings: mfd: Convert atmel-flexcom to json-schema
Date: Tue, 13 Sep 2022 10:16:18 +0000	[thread overview]
Message-ID: <CO1PR11MB4865D623FA957BE718C7A75292479@CO1PR11MB4865.namprd11.prod.outlook.com> (raw)
In-Reply-To: <98ab5118-aa32-af20-a732-dcb5e362717b@linaro.org>

> On 13/09/2022 07:29, Kavyasree.Kotagiri@microchip.com wrote:
> >>>>> flexcom@fc018000: spi@400: Unevaluated properties are not allowed
> >>>> ('dma-
> >>>>> names', 'dmas' were unexpected)
> >>>>>         arch/arm/boot/dts/at91-kizbox3-hs.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d27_som1_ek.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d27_wlsom1_ek.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d2_icp.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d2_ptc_ek.dtb
> >>>>>         arch/arm/boot/dts/at91-sama5d2_xplained.dtb
> >>>>
> >>>> dma properties for spi node is already being covered by Sergiu in below
> >>>> patch:
> >>>> https://lore.kernel.org/lkml/b4625526-8f9b-ada8-f854-
> >>>> 751a48545576@linaro.org/
> >>>>
> >>> Hi Rob, Please let me know your comments.
> >>
> >> this means it cannot be currently tested. Are you sure that there are no
> >> warnings in all DTBs with your patches?
> >>
> > Yes, I ran dtbs_check. I don’t see any warnings.
> 
> Then the warning could be probably ignored (I assume it is really fixed
> when both patchsets land).
> 
Yes. You are right.

> 
> Best regards,
> Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-13 10:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 15:06 [RESEND PATCH v9 0/3] Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-09-08 15:06 ` Kavyasree Kotagiri
2022-09-08 15:06 ` [RESEND PATCH v9 1/3] dt-bindings: mfd: Convert atmel-flexcom to json-schema Kavyasree Kotagiri
2022-09-08 15:06   ` Kavyasree Kotagiri
2022-09-08 15:13   ` Krzysztof Kozlowski
2022-09-08 15:13     ` Krzysztof Kozlowski
2022-09-08 21:16   ` Rob Herring
2022-09-08 21:16     ` Rob Herring
2022-09-09  6:18     ` Kavyasree.Kotagiri
2022-09-09  6:18       ` Kavyasree.Kotagiri
2022-09-12  8:16       ` Kavyasree.Kotagiri
2022-09-12  8:16         ` Kavyasree.Kotagiri
2022-09-12 11:03         ` Krzysztof Kozlowski
2022-09-12 11:03           ` Krzysztof Kozlowski
2022-09-13  5:29           ` Kavyasree.Kotagiri
2022-09-13  5:29             ` Kavyasree.Kotagiri
2022-09-13  9:15             ` Krzysztof Kozlowski
2022-09-13  9:15               ` Krzysztof Kozlowski
2022-09-13 10:16               ` Kavyasree.Kotagiri [this message]
2022-09-13 10:16                 ` Kavyasree.Kotagiri
2022-09-14  4:56                 ` Kavyasree.Kotagiri
2022-09-14  4:56                   ` Kavyasree.Kotagiri
2022-09-08 15:06 ` [RESEND PATCH v9 2/3] dt-bindings: mfd: atmel,sama5d2-flexcom: Add new compatible string for lan966x Kavyasree Kotagiri
2022-09-08 15:06   ` Kavyasree Kotagiri
2022-09-08 15:14   ` Krzysztof Kozlowski
2022-09-08 15:14     ` Krzysztof Kozlowski
2022-09-09  6:26     ` Kavyasree.Kotagiri
2022-09-09  6:26       ` Kavyasree.Kotagiri
2022-09-08 15:06 ` [RESEND PATCH v9 3/3] mfd: atmel-flexcom: Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-09-08 15:06   ` Kavyasree Kotagiri
2022-09-08 15:21   ` Kavyasree.Kotagiri
2022-09-08 15:21     ` Kavyasree.Kotagiri
2022-09-15  9:11 ` [RESEND PATCH v9 0/3] " Kavyasree.Kotagiri
2022-09-15  9:11   ` Kavyasree.Kotagiri

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=CO1PR11MB4865D623FA957BE718C7A75292479@CO1PR11MB4865.namprd11.prod.outlook.com \
    --to=kavyasree.kotagiri@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Sergiu.Moga@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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 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.