From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media@vger.kernel.org
Subject: [PATCH -next] v4l: expose function outside of ifdef/endif block
Date: Fri, 12 Jun 2009 11:47:42 -0700 [thread overview]
Message-ID: <4A32A2CE.40002@oracle.com> (raw)
In-Reply-To: <20090612185601.be53b034.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Move v4l_bound_align_image() outside of an #ifdef CONFIG_I2C block
so that it is always built. Fixes a build error:
vivi.c:(.text+0x48e26): undefined reference to `v4l_bound_align_image'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/media/video/v4l2-common.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- linux-next-20090612.orig/drivers/media/video/v4l2-common.c
+++ linux-next-20090612/drivers/media/video/v4l2-common.c
@@ -915,6 +915,7 @@ const unsigned short *v4l2_i2c_tuner_add
return NULL;
}
EXPORT_SYMBOL_GPL(v4l2_i2c_tuner_addrs);
+#endif
/* Clamp x to be between min and max, aligned to a multiple of 2^align. min
* and max don't have to be aligned, but there must be at least one valid
@@ -986,5 +987,3 @@ void v4l_bound_align_image(u32 *w, unsig
}
}
EXPORT_SYMBOL_GPL(v4l_bound_align_image);
-
-#endif
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next prev parent reply other threads:[~2009-06-12 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 8:56 linux-next: Tree for June 12 Stephen Rothwell
2009-06-12 18:47 ` Randy Dunlap [this message]
2009-06-12 19:31 ` [PATCH -next] v4l: expose function outside of ifdef/endif block Trent Piepho
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=4A32A2CE.40002@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=mchehab@infradead.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