devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Gerhard Engleder <gerhard@engleder-embedded.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/6] dt-bindings: net: tsnep: Allow dma-coherent
Date: Sun, 25 Sep 2022 09:41:21 +0200	[thread overview]
Message-ID: <7c7f67d3-d42e-a053-256d-706cc9dfb947@linaro.org> (raw)
In-Reply-To: <773e8425-58ff-1f17-f0eb-2041f3114105@engleder-embedded.com>

On 24/09/2022 20:11, Gerhard Engleder wrote:
> On 24.09.22 11:15, Krzysztof Kozlowski wrote:
>> On 23/09/2022 22:29, Gerhard Engleder wrote:
>>> Fix the following dtbs_check error if dma-coherent is used:
>>>
>>> ...: 'dma-coherent' does not match any of the regexes: 'pinctrl-[0-9]+'
>>>  From schema: .../Documentation/devicetree/bindings/net/engleder,tsnep.yaml
>>
>> Skip last line - it's obvious. What instead you miss here - the
>> DTS/target which has this warning. I assume that some existing DTS uses
>> this property?
> 
> I will skip that line.
> 
> The binding is for an FPGA based Ethernet MAC. I'm working with
> an evaluation platform currently. The DTS for the evaluation platform
> is mainline, but my derived DTS was not accepted mainline. So there is
> no DTS. This is similar for other FPGA based devices.

If this is not coming from mainline, then there is no warning...  we are
not interested in warnings in out-of-tree code, because we are not
fixing them.

Best regards,
Krzysztof


  reply	other threads:[~2022-09-25  7:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 20:29 [PATCH net-next v3 0/6] tsnep: multi queue support and some other improvements Gerhard Engleder
2022-09-23 20:29 ` [PATCH net-next v3 1/6] dt-bindings: net: tsnep: Allow dma-coherent Gerhard Engleder
2022-09-24  9:15   ` Krzysztof Kozlowski
2022-09-24 18:11     ` Gerhard Engleder
2022-09-25  7:41       ` Krzysztof Kozlowski [this message]
2022-09-25  8:14         ` Gerhard Engleder
2022-09-26  8:55           ` Krzysztof Kozlowski
2022-09-26 17:46             ` Gerhard Engleder
2022-09-28  7:17               ` Krzysztof Kozlowski
2022-09-23 20:29 ` [PATCH net-next v3 2/6] dt-bindings: net: tsnep: Allow additional interrupts Gerhard Engleder
2022-09-24  9:17   ` Krzysztof Kozlowski
2022-09-24 19:06     ` Gerhard Engleder
2022-09-23 20:29 ` [PATCH net-next v3 3/6] tsnep: Move interrupt from device to queue Gerhard Engleder
2022-09-23 20:29 ` [PATCH net-next v3 4/6] tsnep: Support multiple TX/RX queue pairs Gerhard Engleder
2022-09-23 20:29 ` [PATCH net-next v3 5/6] tsnep: Add EtherType RX flow classification support Gerhard Engleder
2022-09-23 20:29 ` [PATCH net-next v3 6/6] tsnep: Use page pool for RX Gerhard Engleder

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=7c7f67d3-d42e-a053-256d-706cc9dfb947@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=gerhard@engleder-embedded.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@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).