Date:   Tue, 7 Dec 2021 13:11:02 +0000
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'
Message-ID: <Ya9dZiqbSPODo74p@sirena.org.uk>
References: <202112070621.TnLPiADU-lkp@intel.com>
 <13326272.At7iLaMNiz@archbook>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="Bu7aYMSE//vud9rI"
Content-Disposition: inline
In-Reply-To: <13326272.At7iLaMNiz@archbook>
Precedence: bulk


--Bu7aYMSE//vud9rI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

--Bu7aYMSE//vud9rI
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmGvXWUACgkQJNaLcl1U
h9DDtQf/QZ2O0UkGXzLJfaag+pGtz/017d0AGj7BA0ugsyy0dB8xIlUUzPZdCCsY
ugIVwiX0znypgeZ236g4K4X+YIstYIFVjAKxQ9WftgTGS8JJfw3I0E2ZI0N8SHHm
sPoS6TismjwwcSg0YtYB2bXzgq/Ld3xqfVzvLqwY+KHHqOX8EomVXJ12XqDIyQc+
nUaNnHWO+++ueuqtdumGG6oi1sleixFujOFwySkM/fno1iXWNH3M1ONHepaikfjG
0fI1VpbBYBABWz5sTEeekLGM6T9Od24O83G7Nnth1FN6bhWuD41iqjgdVtrb1TfD
ZN7qK1WrUp+cczm4Gutn8Jl6FMUuAw==
=08a9
-----END PGP SIGNATURE-----

--Bu7aYMSE//vud9rI--