Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Thu, 5 May 2022 16:04:45 +0200
From:   Thierry Reding <thierry.reding@gmail.com>
To:     Dipen Patel <dipenp@nvidia.com>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the hte tree
Message-ID: <YnPZffmJQjuU+8fI@orome>
References: <20220504165956.531c4b53@canb.auug.org.au>
 <YnIlh++OJDRrK9sz@orome>
 <05e94e6a-86d3-5d60-081a-6adb3bcafb35@nvidia.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="O5mwXgebHMGAcL4s"
Content-Disposition: inline
In-Reply-To: <05e94e6a-86d3-5d60-081a-6adb3bcafb35@nvidia.com>
User-Agent: Mutt/2.2.1 (c8109e14) (2022-02-19)
Precedence: bulk


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

On Wed, May 04, 2022 at 08:17:50PM -0700, Dipen Patel wrote:
> Hi Stephen, Thierry,
>=20
> Before sending patches I compiled and tested with or without HTE
> config successfully, I used gcc arm64 cross compiler. The initial
> problem kernel boat reported (reproduce step snippet below) used clang
> as compiler and that gives typedef issue which is what hte_return_t
> is. Do you know if we have to treat it differently with clang vs gcc
> or did I miss something?

It's probably a good idea to do builds with clang at this point since
apparently it can catch some cases that GCC doesn't. There's some
documentation on how to do that here:

	https://www.kernel.org/doc/html/latest/kbuild/llvm.html

The process is quite similar to using GCC and it has the advantage that
clang ships with built-in cross-compilers, so less hassle setting things
up.

> However below failure seems like (correct me if I am wrong) Thierry
> might have changed typedef to int in one place and possibly not all
> other places.

Yes, the hte_return_t failures were my fault. Turns out due to some
dependencies not being fulfilled my test builds didn't cover gpiolib
character devices, so I didn't catch those.

I've not got a couple of configurations that I can build and a short
script that will verify that all the necessary files have been built, so
that should hopefully catch such issues in the future.

I had also pushed a fixed branch yesterday and it looks like today's
linux-next built fine for HTE, so it's now included.

Thierry

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

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

iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAmJz2XoACgkQ3SOs138+
s6HoSBAAwQs15GtRNFYlV1kr9YD8yqmVtD8o82iqw8LmgYh3ZP/4DJ1i+D3y3xJC
JmM8bd4ItK5cwrY47TNDb2m6xATCgJoMWOu7Pe+mEI6Ens00srFVuIKBMLuNXiFt
oWwD5CxOD9SYc4LUAYN58xyVszbWv5u3Ml6glQrlhid0ybyO3Mr/5LJpCUsUejth
sbf9dHzHJdTwgCy0Gw4i9L/qMX+VNYG89Q6+pmdh5PQdD67fDRh7XTJr8krt9Y8L
POfWZ3yg6mwSscepsJa4FrZlUZAjCjTVa5wp6s4PhETaQvT9yFlH57wNbTdT8WMB
UAoptDhThSoeqkVfEZcoEfRJ1p7XKaRs+XsitK7Kld7bULSgIyOKHzg32bT9Bo/r
B67X1iuwydXi2uybD6nVLG6hBgD88BfPXFgLtVSO0iLd3HfXwIB8c9FTebd/upAE
f62a2cmcfin8M4DZz+b7Pk6Mp31fYEvPMMg5xxrO7iglJpFMk0enPgTm/G8CgJ9l
Bz4ZD+w3mkephSXw1qj5cBqdxpnTG6sCkObjizT5oXF7KPlAOcogc8Jg69rwu8mh
53R6awLJIxnDE6dmS+jpE6DaHn9AiY/LJ14nSwUjIxDD3iTXEOewbS6+mQLApQBr
HietW2z/oL/9cFHBgMRMa39kYcA8QsSqZSc6ztQkwgqtoJl8c5c=
=I36G
-----END PGP SIGNATURE-----

--O5mwXgebHMGAcL4s--