[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdiRH_J8QUALDNufdWh0eNnKsTmp5q+RGBassFdMcpEmw@mail.gmail.com>
Date: Tue, 28 Aug 2018 20:03:23 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Sam Protsenko <semen.protsenko@...aro.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
codalist@...a.cs.cmu.edu, coda@...cmu.edu, jaharkes@...cmu.edu,
"James E . J . Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Praneeth Bajjuri <praneeth@...com>, paul.sokolovsky@...aro.org,
mszeredi@...e.cz, sumit.semwal@...aro.org,
Ruslan Bilovol <ruslan.bilovol@...il.com>
Subject: Re: [PATCH 1/2] codafs: Fix build using bare-metal toolchain
On Tue, Aug 28, 2018 at 5:24 PM Sam Protsenko
<semen.protsenko@...aro.org> wrote:
>
> The kernel is self-contained project and can be built with bare-metal
> toolchain. But bare-metal toolchain doesn't define u_quad_t type.
> Because of this codafs build fails when building with bare-metal
> toolchain. This patch fixes it by defining u_quad_t type in case when
> non-Linux toolchain is used.
> #endif /* !KERNEL */
I'm wondering what the heck KERNEL is doing in UAPI header.
Looks like this header is split wrongly in the first place.
> +#if defined(__KERNEL__) && !defined(__linux__) && !defined(_UQUAD_T_) && \
P.S. Actually it's the only header which uses KERNEL in UAPI.
Definitely it should be fixed first.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists