From: Stephen Boyd <sboyd@kernel.org>
To: Claudiu.Beznea@microchip.com, Ludovic.Desroches@microchip.com,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
mark.rutland@arm.com, mturquette@baylibre.com,
robh+dt@kernel.org
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Claudiu.Beznea@microchip.com
Subject: Re: [PATCH v4 1/4] clk: at91: sckc: sama5d4 has no bypass support
Date: Wed, 26 Jun 2019 11:34:47 -0700 [thread overview]
Message-ID: <20190626183448.2C47B216FD@mail.kernel.org> (raw)
In-Reply-To: <1558433454-27971-2-git-send-email-claudiu.beznea@microchip.com>
Quoting Claudiu.Beznea@microchip.com (2019-05-21 03:11:22)
> From: Claudiu Beznea <claudiu.beznea@microchip.com>
>
> The slow clock of SAMA5D4 has no bypass support thus remove it.
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2019-06-26 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 10:11 [PATCH v4 0/4] add slow clock support for SAM9X60 Claudiu.Beznea
2019-05-21 10:11 ` [PATCH v4 1/4] clk: at91: sckc: sama5d4 has no bypass support Claudiu.Beznea
2019-06-26 18:34 ` Stephen Boyd [this message]
2019-05-21 10:11 ` [PATCH v4 2/4] clk: at91: sckc: add support to specify registers bit offsets Claudiu.Beznea
2019-05-21 10:49 ` Alexandre Belloni
2019-06-26 18:34 ` Stephen Boyd
2019-05-21 10:11 ` [PATCH v4 3/4] dt-bindings: clk: at91: add bindings for SAM9X60's slow clock controller Claudiu.Beznea
2019-06-26 18:34 ` Stephen Boyd
2019-05-21 10:11 ` [PATCH v4 4/4] clk: at91: sckc: add support for SAM9X60 Claudiu.Beznea
2019-06-26 18:34 ` Stephen Boyd
2019-06-26 18:36 ` Stephen Boyd
2019-06-27 10:23 ` Claudiu.Beznea
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=20190626183448.2C47B216FD@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.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).