From: Mark Brown <broonie@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: rockchip_i2s_tdm.c:undefined reference to `clk_set_parent'
Date: Tue, 07 Dec 2021 13:11:02 +0000 [thread overview]
Message-ID: <Ya9dZiqbSPODo74p@sirena.org.uk> (raw)
In-Reply-To: <13326272.At7iLaMNiz@archbook>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On Tue, Dec 07, 2021 at 12:32:52PM +0100, Nicolas Frattaroli wrote:
> So my question is: do I need to care about this? This hardware
> will never be used on MIPS, and a lot of other drivers (as seen in
> the errors snippet from the test robot) have the same issue, and
> the problem is most likely not in my driver but in that specific
> configuration's clock API implementation.
It's fine, in theory you should care and add suitable dependencies but
in practice it's not bothering anyone and at this point I'd rather see
this sorted on the MIPS side, supporting things like this is just
ongoing hassle.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: rockchip_i2s_tdm.c:undefined reference to `clk_set_parent'
Date: Tue, 7 Dec 2021 13:11:02 +0000 [thread overview]
Message-ID: <Ya9dZiqbSPODo74p@sirena.org.uk> (raw)
In-Reply-To: <13326272.At7iLaMNiz@archbook>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
On Tue, Dec 07, 2021 at 12:32:52PM +0100, Nicolas Frattaroli wrote:
> So my question is: do I need to care about this? This hardware
> will never be used on MIPS, and a lot of other drivers (as seen in
> the errors snippet from the test robot) have the same issue, and
> the problem is most likely not in my driver but in that specific
> configuration's clock API implementation.
It's fine, in theory you should care and add suitable dependencies but
in practice it's not bothering anyone and at this point I'd rather see
this sorted on the MIPS side, supporting things like this is just
ongoing hassle.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-07 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 22:46 rockchip_i2s_tdm.c:undefined reference to `clk_set_parent' kernel test robot
2021-12-06 22:46 ` kernel test robot
2021-12-07 11:32 ` Nicolas Frattaroli
2021-12-07 11:32 ` Nicolas Frattaroli
2021-12-07 13:11 ` Mark Brown [this message]
2021-12-07 13:11 ` Mark Brown
2021-12-11 19:47 ` Randy Dunlap
2021-12-11 19:47 ` Randy Dunlap
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=Ya9dZiqbSPODo74p@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.