2014-07-29 17:44:49

by Fernando Apesteguia

[permalink] [raw]
Subject: [PATCH] staging: vt6655: Fix device table definition.

From: Fernando Apesteguia <[email protected]>

Add static to the definition of the pci device table.

Signed-off-by: Fernando Apesteguia <[email protected]>
---
drivers/staging/vt6655/device_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c
index 1d3908d..99a1f97 100644
--- a/drivers/staging/vt6655/device_main.c
+++ b/drivers/staging/vt6655/device_main.c
@@ -260,7 +260,7 @@ static CHIP_INFO chip_info_table[] = {
{0, NULL}
};

-const struct pci_device_id vt6655_pci_id_table[] = {
+static const struct pci_device_id vt6655_pci_id_table[] = {
{ PCI_VDEVICE(VIA, 0x3253), (kernel_ulong_t)chip_info_table},
{ 0, }
};
--
1.7.9.5


2014-07-30 11:43:18

by Tobias Klauser

[permalink] [raw]
Subject: Re: [PATCH] staging: vt6655: Fix device table definition.

On 2014-07-29 at 19:44:24 +0200, [email protected] <[email protected]> wrote:
> From: Fernando Apesteguia <[email protected]>
>
> Add static to the definition of the pci device table.
>
> Signed-off-by: Fernando Apesteguia <[email protected]>

This change is already part of Greg's tree, see commit
9e4c5c2837a4 ("staging: vt6655: statify some variables") in branch
staging-next. Please make sure you work against that branch (which is
also a part of linux-next) for any patches you submit.

Cheers
Tobias

2014-07-30 14:12:37

by Fernando Apesteguia

[permalink] [raw]
Subject: Re: [PATCH] staging: vt6655: Fix device table definition.

On Wed, Jul 30, 2014 at 1:43 PM, Tobias Klauser <[email protected]> wrote:
>
> On 2014-07-29 at 19:44:24 +0200, [email protected] <[email protected]> wrote:
> > From: Fernando Apesteguia <[email protected]>
> >
> > Add static to the definition of the pci device table.
> >
> > Signed-off-by: Fernando Apesteguia <[email protected]>
>
> This change is already part of Greg's tree, see commit
> 9e4c5c2837a4 ("staging: vt6655: statify some variables") in branch
> staging-next. Please make sure you work against that branch (which is
> also a part of linux-next) for any patches you submit.

Ooops. I will. Thanks for the hint!

>
> Cheers
> Tobias