From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus <torvalds@linux-foundation•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Thomas Gleixner <tglx@linutronix•de>,
Samuel Ortiz <sameo@linux•intel.com>,
Tony Lindgren <tony@atomide•com>,
Santosh Shilimkar <santosh.shilimkar@ti•com>,
Balaji T K <balajitk@ti•com>, Rajendra Nayak <rnayak@ti•com>
Subject: linux-next: origin tree build warnings
Date: Fri, 1 Jan 2010 11:42:38 +1100 [thread overview]
Message-ID: <20100101114238.83108321.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hi all,
Today's linux-next build (powerpc allyesconfig) produced these warnings:
drivers/mfd/twl4030-irq.c: In function 'twl4030_sih_do_edge':
drivers/mfd/twl4030-irq.c:571: warning: passing argument 1 of 'spin_lock_irq' from incompatible pointer type
include/linux/spinlock.h:304: note: expected 'struct spinlock_t *' but argument is of type 'struct raw_spinlock_t *'
drivers/mfd/twl4030-irq.c:576: warning: passing argument 1 of 'spin_unlock_irq' from incompatible pointer type
include/linux/spinlock.h:329: note: expected 'struct spinlock_t *' but argument is of type 'struct raw_spinlock_t *'
Introduced by commit 239007b8440abff689632f50cdf0f2b9e895b534 ("genirq:
Convert irq_desc.lock to raw_spinlock"). I guess that this file was
missed in the conversion.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-01-01 0:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 0:42 Stephen Rothwell [this message]
2010-01-01 0:50 ` linux-next: origin tree build warnings Linus Torvalds
2010-01-01 1:22 ` Stephen Rothwell
2010-01-01 1:32 ` Linus Torvalds
2010-01-01 1:50 ` Stephen Rothwell
2010-01-02 9:32 ` Shilimkar, Santosh
2010-01-04 13:51 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2009-04-29 4:44 Stephen Rothwell
2009-04-29 7:52 ` Andrew Morton
2009-04-29 15:38 ` Tyler Hicks
2008-12-29 0:35 Stephen Rothwell
2008-12-29 4:01 ` David Miller
2008-12-29 4:17 ` Stephen Rothwell
2008-12-29 4:21 ` David Miller
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=20100101114238.83108321.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=balajitk@ti$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rnayak@ti$(echo .)com \
--cc=sameo@linux$(echo .)intel.com \
--cc=santosh.shilimkar@ti$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=tony@atomide$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/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