public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Grant Likely <grant.likely@arm.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	nd@arm.com, Jonathan Corbet <corbet@lwn.net>,
	Saravana Kannan <saravanak@google.com>
Subject: Re: [PATCH] Add documentation on meaning of -EPROBE_DEFER
Date: Tue, 31 Mar 2020 18:43:40 +0200	[thread overview]
Message-ID: <20200331164340.GA1821785@kroah.com> (raw)
In-Reply-To: <20200331143355.GP1922688@smile.fi.intel.com>

On Tue, Mar 31, 2020 at 05:33:55PM +0300, Andy Shevchenko wrote:
> On Fri, Mar 27, 2020 at 05:01:32PM +0000, Grant Likely wrote:
> > Add a bit of documentation on what it means when a driver .probe() hook
> > returns the -EPROBE_DEFER error code, including the limitation that
> > -EPROBE_DEFER should be returned as early as possible, before the driver
> > starts to register child devices.
> > 
> > Also: minor markup fixes in the same file
> 
> Greg, can we at least for time being have this documented, means applied?

It's the middle of the merge window, you know I can't take anything in
my trees until after -rc1 is out.

I will queue it up then, thanks.

greg k-h

  reply	other threads:[~2020-03-31 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 17:01 [PATCH] Add documentation on meaning of -EPROBE_DEFER Grant Likely
2020-03-27 18:10 ` Saravana Kannan
2020-03-27 23:25   ` Grant Likely
2020-03-27 23:55     ` Saravana Kannan
2020-03-28 11:13       ` Andy Shevchenko
2020-03-28 17:03       ` Jonathan Corbet
2020-03-28 21:46         ` Saravana Kannan
2020-03-31 14:33 ` Andy Shevchenko
2020-03-31 16:43   ` Greg Kroah-Hartman [this message]
2020-03-31 17:03     ` Andy Shevchenko

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=20200331164340.GA1821785@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=grant.likely@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nd@arm.com \
    --cc=saravanak@google.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