linux-kernel - Re: [PATCH 05/39] cpufreq: nforce2: remove DEFINE_PCI_DEVICE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAOh2x=kKyket469zicV0KgYpeF7EMHSY5iuNSHvnf1b1QSgGjw@mail.gmail.com>
Date:	Tue, 3 Dec 2013 11:24:42 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Jingoo Han <jg1.han@...sung.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH 05/39] cpufreq: nforce2: remove DEFINE_PCI_DEVICE_TABLE macro

On Tue, Dec 3, 2013 at 4:34 AM, Jingoo Han <jg1.han@...sung.com> wrote:
> Don't use DEFINE_PCI_DEVICE_TABLE macro, because this macro
> is not preferred.
>
> Signed-off-by: Jingoo Han <jg1.han@...sung.com>
> ---
>  drivers/cpufreq/cpufreq-nforce2.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cpufreq-nforce2.c b/drivers/cpufreq/cpufreq-nforce2.c
> index a05b876..353ccfa 100644
> --- a/drivers/cpufreq/cpufreq-nforce2.c
> +++ b/drivers/cpufreq/cpufreq-nforce2.c
> @@ -379,7 +379,7 @@ static struct cpufreq_driver nforce2_driver = {
>  };
>
>  #ifdef MODULE
> -static DEFINE_PCI_DEVICE_TABLE(nforce2_ids) = {
> +static const struct pci_device_id nforce2_ids[] = {
>         { PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NFORCE2 },
>         {}
>  };

Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/