From: Sinan Kaya <okaya@codeaurora.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Timur Tabi <timur@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / GED: use late init to allow other drivers init
Date: Mon, 24 Apr 2017 21:43:13 -0400 [thread overview]
Message-ID: <0601c14c-ce5c-a181-0801-4a64a0a3c7be@codeaurora.org> (raw)
In-Reply-To: <CAJZ5v0jaGnoCjiU6VuHLyy9Kug8nHzxPxP8tuy3kphtfgmW38w@mail.gmail.com>
> My point is that nothing guarantees a specific ordering or timing of
> module loading in general, so moving stuff to different initcall
> levels does not really help 100% of the time.
>
Are you talking about init vs. probe in general?
Sorry, I'm trying to decode what you mean to see if there is some other behavior
that I'm not aware of in ACPI.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-04-25 1:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 22:28 [PATCH] ACPI / GED: use late init to allow other drivers init Sinan Kaya
2017-04-21 22:43 ` Rafael J. Wysocki
2017-04-21 22:48 ` Sinan Kaya
2017-04-21 22:48 ` Sinan Kaya
2017-04-24 23:01 ` Rafael J. Wysocki
2017-04-24 23:33 ` Sinan Kaya
2017-04-25 7:01 ` Lukas Wunner
2017-04-25 16:24 ` Sinan Kaya
2017-04-28 2:32 ` Sinan Kaya
2017-05-11 0:58 ` Rafael J. Wysocki
2017-05-11 1:38 ` Sinan Kaya
2017-05-11 0:46 ` Rafael J. Wysocki
2017-05-11 13:43 ` Sinan Kaya
2017-05-11 14:52 ` Rafael J. Wysocki
2017-05-15 2:36 ` Sinan Kaya
2017-05-15 10:59 ` Rafael J. Wysocki
2017-05-21 15:51 ` Sinan Kaya
2017-04-25 1:43 ` Sinan Kaya [this message]
2017-04-25 11:03 ` Rafael J. Wysocki
2017-04-25 16:25 ` Sinan Kaya
2017-04-24 22:49 ` Baicar, Tyler
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=0601c14c-ce5c-a181-0801-4a64a0a3c7be@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=timur@codeaurora.org \
/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;
as well as URLs for NNTP newsgroup(s).