public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ulf Hansson <ulf.hansson@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Takeshi Saito <takeshi.saito.xv@renesas•com>,
	Wolfram Sang <wsa+renesas@sang-engineering•com>,
	Simon Horman <horms+renesas@verge•net.au>
Subject: linux-next: build failure after merge of the mmc-fixes tree
Date: Tue, 26 Feb 2019 08:22:00 +1100	[thread overview]
Message-ID: <20190226082200.4f7aa469@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-02-25 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25 21:22 Stephen Rothwell [this message]
2019-02-27  9:43 ` linux-next: build failure after merge of the mmc-fixes tree Ulf Hansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190226082200.4f7aa469@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=horms+renesas@verge$(echo .)net.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=takeshi.saito.xv@renesas$(echo .)com \
    --cc=ulf.hansson@linaro$(echo .)org \
    --cc=wsa+renesas@sang-engineering$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox