From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-media@vger.kernel.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 4 (media/radio)
Date: Mon, 4 Jul 2011 13:31:57 -0700 [thread overview]
Message-ID: <20110704133157.7a37d8d9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110704170952.1024e89b.sfr@canb.auug.org.au>
On Mon, 4 Jul 2011 17:09:52 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20110701:
>
> The v4l-dvb tree gained a build failure so I used the version from
> next-20110701.
drivers/media/radio/radio-rtrack2.c:31:17: error: invalid suffix "c" on integer constant
make[4]: [drivers/media/radio/radio-rtrack2.o] Error 1 (ignored)
drivers/media/radio/radio-aimslab.c:49:17: error: invalid suffix "f" on integer constant
make[4]: [drivers/media/radio/radio-aimslab.o] Error 1 (ignored)
drivers/media/radio/radio-gemtek.c:51:18: error: invalid suffix "c" on integer constant
make[4]: [drivers/media/radio/radio-gemtek.o] Error 1 (ignored)
drivers/media/radio/radio-zoltrix.c:51:17: error: invalid suffix "c" on integer constant
These drivers do not handle hex CONFIG_ values correctly.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-04 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 7:09 linux-next: Tree for July 4 Stephen Rothwell
2011-07-04 20:31 ` Randy Dunlap [this message]
2011-07-04 20:45 ` linux-next: Tree for July 4 (misc/pti) Randy Dunlap
2011-07-07 15:14 ` Randy Dunlap
2011-07-07 16:29 ` J Freyensee
2011-07-07 16:32 ` Randy Dunlap
2011-07-07 16:34 ` J Freyensee
2011-07-07 16:42 ` Randy Dunlap
2011-07-08 20:07 ` Geert Uytterhoeven
2011-07-08 21:24 ` J Freyensee
2011-07-08 21:31 ` Randy Dunlap
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=20110704133157.7a37d8d9.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
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;
as well as URLs for NNTP newsgroup(s).