From: Rob Herring <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, ulf.hansson@linaro.org,
nicolas.ferre@microchip.com, adrian.hunter@intel.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, claudiu.beznea@microchip.com,
Eugen.Hristev@microchip.com,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: sdhci-of-at91: new compatible string and update properties
Date: Mon, 14 Oct 2019 13:11:35 -0500 [thread overview]
Message-ID: <20191014181135.GA4428@bogus> (raw)
In-Reply-To: <20191011103340.26749-1-ludovic.desroches@microchip.com>
On Fri, 11 Oct 2019 12:33:37 +0200, Ludovic Desroches wrote:
> There is a new compatible string for the SAM9X60 sdhci device. It involves
> an update of the properties about the clocks stuff.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
> ---
>
> Changes:
> - v2: remove the extra example and fix node label
>
> This patch conflicts with Nicolas' one: "dt-bindings: sdhci-of-at91: add
> the microchip,sdcal-inverted property". Let me know which one has to be
> rebased or you can handle it.
>
> Ludovic
>
>
> .../devicetree/bindings/mmc/sdhci-atmel.txt | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-10-14 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 10:33 [PATCH v2 1/3] dt-bindings: sdhci-of-at91: new compatible string and update properties Ludovic Desroches
2019-10-11 10:33 ` [PATCH v2 2/3] mmc: sdhci-of-at91: rework clocks management to support SAM9x60 device Ludovic Desroches
2019-10-11 10:33 ` [PATCH v2 3/3] ARM: dts: at91: sama5d2: set the sdmmc gclk frequency Ludovic Desroches
2019-10-14 18:11 ` Rob Herring [this message]
2019-10-18 10:56 ` [PATCH v2 1/3] dt-bindings: sdhci-of-at91: new compatible string and update properties Ulf Hansson
2019-10-18 12:15 ` Ludovic Desroches
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=20191014181135.GA4428@bogus \
--to=robh@kernel.org \
--cc=Eugen.Hristev@microchip.com \
--cc=adrian.hunter@intel.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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).