linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sandeep Patil <sspatil@android.com>
Cc: Saravana Kannan <saravanak@google.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	David Collins <collinsd@codeaurora.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@android.com
Subject: Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering
Date: Tue, 25 Jun 2019 11:53:13 +0800	[thread overview]
Message-ID: <20190625035313.GA13239@kroah.com> (raw)
In-Reply-To: <20190624223707.GH203031@google.com>

On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote:
> We are trying to make sure that all (most) drivers in an Aarch64 system can
> be kernel modules for Android, like any other desktop system for
> example. There are a number of problems we need to fix before that happens
> ofcourse.

I will argue that this is NOT an android-specific issue.  If the goal of
creating an arm64 kernel that will "just work" for a wide range of
hardware configurations without rebuilding is going to happen, we need
to solve this problem with DT.  This goal was one of the original wishes
of the arm64 development effort, let's not loose sight of it as
obviously, this is not working properly just yet.

It just seems that Android is the first one to actually try and
implement that goal :)

thanks,

greg k-h

  reply	other threads:[~2019-06-25  3:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04  0:32 [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering Saravana Kannan
2019-06-04  0:32 ` [RESEND PATCH v1 1/5] of/platform: Speed up of_find_device_by_node() Saravana Kannan
2019-06-10 17:36   ` Rob Herring
     [not found]     ` <CAGETcx_Kb3+fFYHhBUdVbCSNTk4v5j1Ket=Et2ZQY0SHUgLLMw@mail.gmail.com>
2019-06-10 21:07       ` Rob Herring
2019-06-11 15:18     ` Frank Rowand
2019-06-11 20:56       ` Saravana Kannan
2019-06-11 21:52         ` Sandeep Patil
2019-06-12 13:53           ` Rob Herring
2019-06-12 14:21             ` Greg Kroah-Hartman
2019-06-12 16:53               ` Rob Herring
2019-06-12 17:08                 ` Greg Kroah-Hartman
2019-06-12 18:19                   ` Rob Herring
2019-06-12 19:29                     ` Saravana Kannan
2019-06-12 20:23                       ` Frank Rowand
2019-06-12 21:12                       ` Rob Herring
2019-06-12 22:10                         ` Saravana Kannan
2019-06-18 20:47                       ` Sandeep Patil
2019-06-18 21:22                         ` Saravana Kannan
2019-06-12 17:03               ` Frank Rowand
2019-06-12 16:07             ` Frank Rowand
2019-06-12 16:47               ` Frank Rowand
2019-06-12 19:03             ` Frank Rowand
2019-06-04  0:32 ` [RESEND PATCH v1 2/5] driver core: Add device links support for pending links to suppliers Saravana Kannan
2019-06-04  0:32 ` [RESEND PATCH v1 3/5] dt-bindings: Add depends-on property Saravana Kannan
2019-06-12 14:45   ` Sudeep Holla
2019-06-04  0:32 ` [RESEND PATCH v1 4/5] of/platform: Add functional dependency link from "depends-on" property Saravana Kannan
2019-06-04  0:32 ` [RESEND PATCH v1 5/5] driver core: Add sync_state driver/bus callback Saravana Kannan
2019-06-12 21:21 ` [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering Frank Rowand
2019-06-13 13:19   ` Rob Herring
2019-06-24 22:37 ` Sandeep Patil
2019-06-25  3:53   ` Greg Kroah-Hartman [this message]
2019-06-26  4:30     ` Sandeep Patil
2019-06-26  5:49       ` Frank Rowand
2019-06-26 21:30     ` Rob Herring
2019-06-28  2:36       ` Saravana Kannan

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=20190625035313.GA13239@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=collinsd@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=saravanak@google.com \
    --cc=sspatil@android.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;
as well as URLs for NNTP newsgroup(s).