[an error occurred while processing this directive]
|
|
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPDyKFoXY2wx+HoVEJuPGEJnmUYYK+sCEGEDWhAKJ9bV5zytkg@mail.gmail.com>
Date: Wed, 27 Feb 2019 10:43:15 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Takeshi Saito <takeshi.saito.xv@...esas.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Simon Horman <horms+renesas@...ge.net.au>
Subject: Re: linux-next: build failure after merge of the mmc-fixes tree
On Mon, 25 Feb 2019 at 22:22, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi Ulf,
>
> After merging the mmc-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/mmc/host/tmio_mmc_core.c: In function 'tmio_mmc_start_data':
> drivers/mmc/host/tmio_mmc_core.c:706:34: error: 'SZ_64K' undeclared (first use in this function); did you mean 'EM_68K'?
> if (host->mmc->max_blk_count >= SZ_64K)
> ^~~~~~
> EM_68K
> drivers/mmc/host/tmio_mmc_core.c:706:34: note: each undeclared identifier is reported only once for each function it appears in
>
> Caused by commit
>
> 063f8fee9927 ("mmc: tmio: fix access width of Block Count Register")
>
> I have reverted that commit for today.
Thanks for letting me know and sorry for the inconvenience! The
offending patch is now amended and should be fixed.
Kind regards
Uffe
Powered by blists - more mailing lists