[PATCH 46/85] drivers: gpu: Move prototype declarations to headerfile radeon_mode.h from radeon_i2c.c

From: Rashika Kheria
Date: Mon Jan 06 2014 - 10:56:24 EST

Move prototype declaration of functions radeon_atom_hw_i2c_xfer() and
radeon_atom_hw_i2c_func() to header file drm/radeon/radeon_mode.h
because they are used by more than one file.

This eliminates the following warnings in drm/radeon/atombios_i2c.c:
drivers/gpu/drm/radeon/atombios_i2c.c:96:5: warning: no previous prototype for âradeon_atom_hw_i2c_xferâ [-Wmissing-prototypes]
drivers/gpu/drm/radeon/atombios_i2c.c:146:5: warning: no previous prototype for âradeon_atom_hw_i2c_funcâ [-Wmissing-prototypes]

Signed-off-by: Rashika Kheria <rashika.kheria@xxxxxxxxx>
Reviewed-by: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
drivers/gpu/drm/radeon/radeon_i2c.c | 4 ----
drivers/gpu/drm/radeon/radeon_mode.h | 4 ++++
2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/radeon/radeon_i2c.c b/drivers/gpu/drm/radeon/radeon_i2c.c
index fc60b74..fd07db8 100644
--- a/drivers/gpu/drm/radeon/radeon_i2c.c
+++ b/drivers/gpu/drm/radeon/radeon_i2c.c
@@ -31,10 +31,6 @@
#include "radeon.h"
#include "atom.h"

-extern int radeon_atom_hw_i2c_xfer(struct i2c_adapter *i2c_adap,
- struct i2c_msg *msgs, int num);
-extern u32 radeon_atom_hw_i2c_func(struct i2c_adapter *adap);
* radeon_ddc_probe
diff --git a/drivers/gpu/drm/radeon/radeon_mode.h b/drivers/gpu/drm/radeon/radeon_mode.h
index 8f2f4a3..129f069 100644
--- a/drivers/gpu/drm/radeon/radeon_mode.h
+++ b/drivers/gpu/drm/radeon/radeon_mode.h
@@ -628,6 +628,10 @@ struct atom_voltage_table
struct atom_voltage_table_entry entries[MAX_VOLTAGE_ENTRIES];

+int radeon_atom_hw_i2c_xfer(struct i2c_adapter *i2c_adap,
+ struct i2c_msg *msgs, int num);
+u32 radeon_atom_hw_i2c_func(struct i2c_adapter *adap);
radeon_atom_backlight_init(struct radeon_encoder *radeon_encoder,
struct drm_connector *drm_connector);

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/