linux-kernel - Re: [PATCH 1/2] EDAC: add __init to i7core_xeon_pci

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091204155428.307e612d@jbarnes-piketon>
Date:	Fri, 4 Dec 2009 15:54:28 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	jirislaby@...il.com, linux-kernel@...r.kernel.org,
	Mauro Carvalho Chehab <mchehab@...hat.com>
Subject: Re: [PATCH 1/2] EDAC: add __init to i7core_xeon_pci_fixup

On Mon, 30 Nov 2009 21:19:41 +0100
Jiri Slaby <jslaby@...e.cz> wrote:

> It's called only from an __init function and is the only user
> of pcibios_scan_specific_bus which will be marked as __devinit in
> the next patch.
> 
> Signed-off-by: Jiri Slaby <jslaby@...e.cz>
> Cc: Mauro Carvalho Chehab <mchehab@...hat.com>
> ---
>  drivers/edac/i7core_edac.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/edac/i7core_edac.c b/drivers/edac/i7core_edac.c
> index 4de5a18..c7fc0d5 100644
> --- a/drivers/edac/i7core_edac.c
> +++ b/drivers/edac/i7core_edac.c
> @@ -1141,7 +1141,7 @@ static void i7core_put_all_devices(void)
>  		i7core_put_devices(i7core_dev);
>  }
>  
> -static void i7core_xeon_pci_fixup(int dev_id)
> +static void __init i7core_xeon_pci_fixup(int dev_id)
>  {
>  	struct pci_dev *pdev = NULL;
>  	int i;

I don't know who handles EDAC patches, but I'm pretty sure it's not
me. :)  It doesn't apply to my tree anyway, so it probably needs a
refresh.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/