linux-kernel - Re: [PATCH]PCIE ASPM support

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]

Date:	Tue, 15 Jan 2008 05:22:01 -0700
From:	Matthew Wilcox <matthew@....cx>
To:	Shaohua Li <shaohua.li@...el.com>
Cc:	linux-pci <linux-pci@...ey.karlin.mff.cuni.cz>,
	Greg KH <greg@...ah.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	"Kok, Auke" <auke-jan.h.kok@...el.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH]PCIE ASPM support - takes 2

On Tue, Jan 15, 2008 at 01:07:02PM +0800, Shaohua Li wrote:
> > > +
> > > +/* Called after ACPI is enabled */
> > > +static int __init acpi_pcie_support_init(void)
> > > +{
> > > +	pcie_aspm_init();
> > > +	return 0;
> > > +}
> > > +fs_initcall(acpi_pcie_support_init);
> > 
> > Is there any reason to put this in here instead of just making
> > pcie_aspm_init an initcall?
> yes, this will evaluate some ACPI methods, so must be called after ACPI
> is initialized, which is a sub_system call

I wasn't saying that you should change it from being an fs_initcall.  I
was saying that you might want to consider deleting this function and
adding

fs_initcall(pcie_aspm_init);

in the file that defines pcie_aspm_init.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/