[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACPK8Xf1g2fp5X3ELBUyjzP6Fmvt1XWLU_UgCKdZaDVjdyKryQ@mail.gmail.com>
Date: Fri, 27 Aug 2021 05:48:50 +0000
From: Joel Stanley <joel@....id.au>
To: ChiaWei Wang <chiawei_wang@...eedtech.com>
Cc: kernel test robot <lkp@...el.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"andrew@...id.au" <andrew@...id.au>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kbuild-all@...ts.01.org" <kbuild-all@...ts.01.org>
Subject: Re: [PATCH v3 3/4] soc: aspeed: Add eSPI driver
On Fri, 27 Aug 2021 at 03:52, ChiaWei Wang <chiawei_wang@...eedtech.com> wrote:
>
> Aspeed 5th and 6th generation SoCs are based on the ARM 32-bits architecture.
> Should we follow the report to make the driver 64-bits compatible?
> Or revise the driver to use more specific data types?
Yes, in general it's expected your driver will compile cleanly for
64-bit architectures. This helps with testing and static analysis,
where CI builds all the drivers for x86.
Cheers,
Joel
Powered by blists - more mailing lists