public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Shaohua Li <shaohua.li@intel.com>
Cc: linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
	Greg KH <greg@kroah.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]PCIE ASPM support - takes 2
Date: Tue, 15 Jan 2008 05:22:01 -0700	[thread overview]
Message-ID: <20080115122200.GW18741@parisc-linux.org> (raw)
In-Reply-To: <1200373622.20869.2.camel@sli10-desk.sh.intel.com>

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."

  reply	other threads:[~2008-01-15 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1200367276.20538.1.camel@sli10-desk.sh.intel.com>
     [not found] ` <20080115041943.GS18741@parisc-linux.org>
2008-01-15  5:07   ` [PATCH]PCIE ASPM support - takes 2 Shaohua Li
2008-01-15 12:22     ` Matthew Wilcox [this message]
2008-01-16  1:14       ` Shaohua Li
2008-01-15  5:02 Shaohua Li
2008-01-16  3:56 ` Valdis.Kletnieks
2008-01-16  5:26   ` Shaohua Li
2008-01-16  9:31     ` Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080115122200.GW18741@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=auke-jan.h.kok@intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=shaohua.li@intel.com \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox