From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Jose Abreu <joabreu@synopsys.com>,
Corentin Labbe <clabbe@baylibre.com>,
"David S. Miller" <davem@davemloft.net>,
Arnd Bergmann <arnd@arndb.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] m68k: coldfire: Normalize clk API
Date: Tue, 12 Jun 2018 23:31:12 +1000 [thread overview]
Message-ID: <e6a2da2c-60e5-b57a-f6c1-3652b8be161c@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdUyD8d2yoe6v8TEinEH3hhS7Znv99pPxDCkr_uEFS0Fzg@mail.gmail.com>
Hi Geert,
On 12/06/18 17:31, Geert Uytterhoeven wrote:
> On Tue, Jun 12, 2018 at 9:27 AM Greg Ungerer <gerg@linux-m68k.org> wrote:
>> On 11/06/18 18:44, Geert Uytterhoeven wrote:
>>> Coldfire still provides its own variant of the clk API rather than using
>>> the generic COMMON_CLK API. This generally works, but it causes some
>>> link errors with drivers using the clk_round_rate(), clk_set_rate(),
>>> clk_set_parent(), or clk_get_parent() functions when a platform lacks
>>> those interfaces.
>>>
>>> This adds empty stub implementations for each of them, and I don't even
>>> try to do something useful here but instead just print a WARN() message
>>> to make it obvious what is going on if they ever end up being called.
>>>
>>> The drivers that call these won't be used on these platforms (otherwise
>>> we'd get a link error today), so the added code is harmless bloat and
>>> will warn about accidental use.
>>>
>>> Based on commit bd7fefe1f06ca6cc ("ARM: w90x900: normalize clk API").
>>>
>>> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>>
>> I am fine with this for ColdFire, so
>>
>> Acked-by: Greg Ungerer <gerg@linux-m68k.org>
>
> Thanks!
>
>> Are you going to take this/these via your m68k git tree?
>
> I''m fine delagating this to you.
No problem. I'll add it to the m68knommu git tree (for-next branch)
when the merge window closes.
Thanks
Greg
next prev parent reply other threads:[~2018-06-12 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 8:44 [PATCH 0/3] Legacy clock drivers: Normalize clk API Geert Uytterhoeven
2018-06-11 8:44 ` [PATCH 1/3] m68k: coldfire: " Geert Uytterhoeven
2018-06-12 7:26 ` Greg Ungerer
2018-06-12 7:31 ` Geert Uytterhoeven
2018-06-12 13:31 ` Greg Ungerer [this message]
2018-06-11 8:44 ` [PATCH 2/3] MIPS: AR7: " Geert Uytterhoeven
2018-06-28 21:31 ` Paul Burton
2018-06-11 8:44 ` [PATCH 3/3 RFC] Revert "net: stmmac: fix build failure due to missing COMMON_CLK dependency" Geert Uytterhoeven
2018-06-11 8:59 ` Arnd Bergmann
2018-06-11 9:13 ` Geert Uytterhoeven
2018-06-12 14:51 ` Jose Abreu
2018-06-11 9:02 ` [PATCH 0/3] Legacy clock drivers: Normalize clk API Arnd Bergmann
2018-06-11 9:09 ` Geert Uytterhoeven
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=e6a2da2c-60e5-b57a-f6c1-3652b8be161c@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jhogan@kernel.org \
--cc=joabreu@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=ralf@linux-mips.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).