linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: daire.mcnamara@microchip.com, cyril.jean@microchip.com,
	linux-i2c@vger.kernel.org, palmer@dabbelt.com,
	robh+dt@kernel.org, padmarao.begari@microchip.com,
	conor.dooley@microchip.com, devicetree@vger.kernel.org,
	lewis.hanly@microchip.com, david.abdurachmanov@gmail.com
Subject: Re: [PATCH v1 1/2] dt-bindings: i2c: microchip: Add Microchip PolarFire host binding
Date: Fri, 25 Jun 2021 16:37:34 +0200	[thread overview]
Message-ID: <YNXqLviYLPEPXPxR@shikoro> (raw)
In-Reply-To: <1620844516.507815.204083.nullmailer@robh.at.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

Hi Rob,

> Documentation/devicetree/bindings/i2c/microchip,mpfs-i2c.example.dts:19:18: fatal error: dt-bindings/clock/microchip,mpfs-clock.h: No such file or directory
>    19 |         #include <dt-bindings/clock/microchip,mpfs-clock.h>
>       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.

I'd think this is only because the file has not hit -next yet?

Would you be so kind and review the bindings nonetheless?

Thank you and kind regards,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-06-25 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 11:20 [PATCH v1 0/2] i2c: microchip: Add driver for PolarFire SoC daire.mcnamara
2021-05-12 11:20 ` [PATCH v1 1/2] dt-bindings: i2c: microchip: Add Microchip PolarFire host binding daire.mcnamara
2021-05-12 18:35   ` Rob Herring
2021-06-25 14:37     ` Wolfram Sang [this message]
2021-05-12 11:20 ` [PATCH v1 2/2] i2c: microchip: Add driver for Microchip PolarFire SoC daire.mcnamara
2021-06-25 14:36   ` Wolfram Sang

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=YNXqLviYLPEPXPxR@shikoro \
    --to=wsa@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=cyril.jean@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=david.abdurachmanov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lewis.hanly@microchip.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=padmarao.begari@microchip.com \
    --cc=palmer@dabbelt.com \
    --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 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).