From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: John Crispin <john@phrozen.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
sergei.shtylyov@gmail.com, thierry.reding@gmail.com,
linux-tegra@vger.kernel.org, balbi@kernel.org, digetx@gmail.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] MIPS: ralink: define stubs for clk_set_parent to fix compile testing
Date: Thu, 25 Mar 2021 11:00:57 +0100 [thread overview]
Message-ID: <20210325100057.GE5775@alpha.franken.de> (raw)
In-Reply-To: <20210317112644.24502-1-krzysztof.kozlowski@canonical.com>
On Wed, Mar 17, 2021 at 12:26:44PM +0100, Krzysztof Kozlowski wrote:
> The Ralink MIPS platform does not use Common Clock Framework and does
> not define certain clock operations leading to compile test failures:
>
> /usr/bin/mips-linux-gnu-ld: drivers/usb/phy/phy-tegra-usb.o: in function `tegra_usb_phy_init':
> phy-tegra-usb.c:(.text+0x1dd4): undefined reference to `clk_get_parent'
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> Acked-by: John Crispin <john@phrozen.org>
>
> ---
>
> Changes since v1:
> 1. Use EXPORT_SYMBOL_GPL like two other stubs in the file.
> 2. Add Ack
> ---
> arch/mips/ralink/clk.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-03-25 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:26 [PATCH v2] MIPS: ralink: define stubs for clk_set_parent to fix compile testing Krzysztof Kozlowski
2021-03-17 22:10 ` Dmitry Osipenko
2021-03-25 10:00 ` Thomas Bogendoerfer [this message]
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=20210325100057.GE5775@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=balbi@kernel.org \
--cc=digetx@gmail.com \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sergei.shtylyov@gmail.com \
--cc=thierry.reding@gmail.com \
/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