Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 4 Jul 2023 17:41:23 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Conor Dooley <conor@kernel.org>
Cc:     William Qiu <william.qiu@starfivetech.com>,
        devicetree@vger.kernel.org, linux-spi@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Emil Renner Berthing <kernel@esmil.dk>,
        Ziv Xu <ziv.xu@starfivetech.com>
Subject: Re: [PATCH v4 2/3] spi: cadence-quadspi: Add clock configuration for
 StarFive JH7110 QSPI
Message-ID: <9de02a94-8043-4355-8925-99e0d1ffb713@sirena.org.uk>
References: <20230704090453.83980-1-william.qiu@starfivetech.com>
 <20230704090453.83980-3-william.qiu@starfivetech.com>
 <20230704-gooey-lair-2bc45bbd163c@spud>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="L4GnaeX8yK5XFQS4"
Content-Disposition: inline
In-Reply-To: <20230704-gooey-lair-2bc45bbd163c@spud>
Precedence: bulk


--L4GnaeX8yK5XFQS4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 04, 2023 at 05:36:03PM +0100, Conor Dooley wrote:
> On Tue, Jul 04, 2023 at 05:04:52PM +0800, William Qiu wrote:
> > Add QSPI clock operation in device probe.
> >=20
> > Signed-off-by: William Qiu <william.qiu@starfivetech.com>
> > Reviewed-by: Hal Feng <hal.feng@starfivetech.com>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202306022017.UbwjjWRN-lkp=
@intel.com/

> These Reported-by tags don't seem correct, given they were reports about
> this patch, not the reason for it - but did you actually check that you
> fixed the errors that the patch produces?

Yeah, the Reported-bys that LKP sends in response to on list patches are
a menace, they just generate noise.

> This particular one seems to complain about a hunk that is still in the
> patch & the CI running on the RISC-V patchwork is complaining about it.

I'm surprised that builds cleanly anywhere...

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmSkS7IACgkQJNaLcl1U
h9Cwygf+Lj0XeLehyPuY28oqR7nq3BMn39mQIj5yXEW09p/l4CZZw5/nQLPSE4Jm
AczOgbi3beJiQmLD3L3d8BAO8JIHTbTJB+KB45GTL9TAUi35rENRnvQ58BEbC3dw
hGRSzWT4MB6NnwWwB5JncAEACtqgigOD5JVivb11GC6+XmH2A5q4FUP3ZtQpM7Yu
XoD8W7cWHhwFz0K/kLW8R/zSjp3F16C0yl3hZaOyuYvfPO4KqBBjnByCpazTyVFp
bdBGgDDW5slxkRAQco2hUBvqyV6zOdqQv5FXPmw7regtL3fn0OnGMjs3p1jZ0Tdn
Kep9GeD7snkKgqCTvEMXpTvpjBgE6Q==
=dkuj
-----END PGP SIGNATURE-----

--L4GnaeX8yK5XFQS4--