From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Mackerras <paulus@samba•org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
linuxppc-dev@ozlabs•org
Cc: linux-next@vger•kernel.org, Becky Bruce <becky.bruce@freescale•com>
Subject: linux-next: tree build warning
Date: Thu, 4 Dec 2008 10:33:07 +1100 [thread overview]
Message-ID: <20081204103307.35003f44.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
Hi all,
Today's linux-next build (powerpc ppc64_defconfig) produced this warning:
drivers/ieee1394/sbp2.c: In function 'sbp2_create_command_orb':
drivers/ieee1394/sbp2.c:1559: warning: unused variable 'dmadev'
Caused by commit 15e09c0ecaab4a1b4a7ed69db536c38948b92279 ("powerpc: Add
sync_*_for_* to dma_ops") from the powerpc tree. The macros added for
!CONFIG_PPC_NEED_DMA_SYNC_OPS should really be static inline functions.
(as akpm says: "program in C not C preprocessor").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-12-03 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 23:33 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-23 6:17 linux-next: tree build warning Stephen Rothwell
2009-04-23 6:43 ` Ingo Molnar
2009-03-31 5:22 Stephen Rothwell
2009-03-16 8:14 Stephen Rothwell
2009-03-20 0:22 ` Neil Brown
2009-03-12 5:48 Stephen Rothwell
2009-03-12 6:37 ` Nick Piggin
2009-03-12 6:42 ` Stephen Rothwell
2008-12-15 13:35 Stephen Rothwell
2008-12-15 13:56 ` Thomas Gleixner
2008-10-28 7:13 Stephen Rothwell
2008-10-30 18:05 ` Christoph Lameter
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=20081204103307.35003f44.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=becky.bruce@freescale$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(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