LKML Archive on lore.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>,
	Douglas Anderson <dianders@chromium.org>,
	Shawn Lin <shawn.lin@rock-chips.com>
Subject: linux-next: build warning after merge of the mmc tree
Date: Thu, 2 Nov 2017 12:36:17 +1100	[thread overview]
Message-ID: <20171102123617.56364a21@canb.auug.org.au> (raw)

Hi Ulf,

After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

In file included from include/linux/irqflags.h:14:0,
                 from arch/arm/include/asm/bitops.h:27,
                 from include/linux/bitops.h:37,
                 from include/linux/kernel.h:10,
                 from include/asm-generic/bug.h:15,
                 from arch/arm/include/asm/bug.h:59,
                 from include/linux/bug.h:4,
                 from include/linux/thread_info.h:11,
                 from include/asm-generic/current.h:4,
                 from ./arch/arm/include/generated/asm/current.h:1,
                 from include/linux/sched.h:11,
                 from include/linux/blkdev.h:4,
                 from drivers/mmc/host/dw_mmc.c:14:
drivers/mmc/host/dw_mmc.c: In function 'dw_mci_set_drto':
include/linux/typecheck.h:11:18: warning: comparison of distinct pointer types lacks a cast
  (void)(&__dummy == &__dummy2); \
                  ^
include/linux/spinlock.h:221:3: note: in expansion of macro 'typecheck'
   typecheck(unsigned long, flags); \
   ^
include/linux/spinlock.h:346:2: note: in expansion of macro 'raw_spin_lock_irqsave'
  raw_spin_lock_irqsave(spinlock_check(lock), flags); \
  ^
drivers/mmc/host/dw_mmc.c:1953:2: note: in expansion of macro 'spin_lock_irqsave'
  spin_lock_irqsave(&host->irq_lock, irqflags);
  ^

Introduced by commit

  80a2a5a7745b ("mmc: dw_mmc: Cleanup the DTO timer like the CTO one")

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2017-11-02  1:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  1:36 Stephen Rothwell [this message]
2017-11-02  1:47 ` Doug Anderson
2017-11-02 15:03   ` Ulf Hansson
2019-03-19  1:15 Stephen Rothwell
2019-10-22  0:47 Stephen Rothwell
2019-10-22  7:31 ` Ulf Hansson
2020-02-19 23:31 Stephen Rothwell
2020-02-20  1:38 ` Baolin Wang
2021-08-25  3:20 Stephen Rothwell

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=20171102123617.56364a21@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@linaro.org \
    --subject='Re: linux-next: build warning after merge of the mmc tree' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).