All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Greg Kroah-Hartman <greg@kroah.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org,
	Manjunath GKondaiah <manjunath.gkondaiah@linaro.org>,
	Dilan Lee <dilee@nvidia.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v3] drivercore: Add driver probe deferral mechanism
Date: Tue, 27 Sep 2011 15:08:49 -0600	[thread overview]
Message-ID: <20110927210849.GD3994@ponder.secretlab.ca> (raw)
In-Reply-To: <201109271550.36427.arnd@arndb.de>

On Tue, Sep 27, 2011 at 03:50:36PM +0200, Arnd Bergmann wrote:
> On Monday 26 September 2011, Grant Likely wrote:
> > Actually, in the next iteration, I'm thinking it would be a good idea
> > to create a new #define to only be used by probe deferral.  I want it
> > to be easy to find all the drivers that are using this mechanism
> > without needing to filter all the unrelated hits.  However, this is a
> > kernel-only thing so it is probably not appropriate to add it to
> > include/asm-generic/errno.h.  I could use some guidance/advice as to
> > the best way to handle this.
> 
> include/linux/errno.h already has a bunch of kernel-internal error
> codes that are never supposed to be seen in user space. Just
> add one there, the next free one right now is 517, after
> ERESTART_RESTARTBLOCK.

Okay, will do.  How does EPROBE_DEFER 518 sound?

g.

WARNING: multiple messages have this Message-ID (diff)
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3] drivercore: Add driver probe deferral mechanism
Date: Tue, 27 Sep 2011 15:08:49 -0600	[thread overview]
Message-ID: <20110927210849.GD3994@ponder.secretlab.ca> (raw)
In-Reply-To: <201109271550.36427.arnd@arndb.de>

On Tue, Sep 27, 2011 at 03:50:36PM +0200, Arnd Bergmann wrote:
> On Monday 26 September 2011, Grant Likely wrote:
> > Actually, in the next iteration, I'm thinking it would be a good idea
> > to create a new #define to only be used by probe deferral.  I want it
> > to be easy to find all the drivers that are using this mechanism
> > without needing to filter all the unrelated hits.  However, this is a
> > kernel-only thing so it is probably not appropriate to add it to
> > include/asm-generic/errno.h.  I could use some guidance/advice as to
> > the best way to handle this.
> 
> include/linux/errno.h already has a bunch of kernel-internal error
> codes that are never supposed to be seen in user space. Just
> add one there, the next free one right now is 517, after
> ERESTART_RESTARTBLOCK.

Okay, will do.  How does EPROBE_DEFER 518 sound?

g.

  reply	other threads:[~2011-09-27 21:18 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 18:51 [RFC PATCH v3] drivercore: Add driver probe deferral mechanism Grant Likely
2011-09-22 18:51 ` Grant Likely
2011-09-22 18:58 ` Joe Perches
2011-09-22 18:58   ` Joe Perches
2011-09-22 19:28 ` David Daney
2011-09-22 20:29 ` Alan Cox
2011-09-22 20:29   ` Alan Cox
2011-09-22 21:19   ` Grant Likely
2011-09-22 21:19     ` Grant Likely
2011-09-23 17:50     ` Valdis.Kletnieks
2011-09-23 17:50       ` Valdis.Kletnieks at vt.edu
2011-09-23 23:18       ` Grant Likely
2011-09-23 23:18         ` Grant Likely
2011-09-22 21:19   ` David Daney
2011-09-22 22:47     ` Alan Cox
2011-09-22 22:47       ` Alan Cox
2011-09-23  5:02       ` Grant Likely
2011-09-23  5:02         ` Grant Likely
2011-09-23 16:55       ` David Daney
2011-09-23 16:55         ` David Daney
2011-09-26 14:16 ` Mark Brown
2011-09-26 14:16   ` Mark Brown
2011-09-26 15:12   ` Russell King - ARM Linux
2011-09-26 15:12     ` Russell King - ARM Linux
2011-09-26 15:26     ` Mark Brown
2011-09-26 15:26       ` Mark Brown
2011-09-26 15:48       ` Grant Likely
2011-09-26 15:48         ` Grant Likely
2011-09-27 13:50         ` Arnd Bergmann
2011-09-27 13:50           ` Arnd Bergmann
2011-09-27 21:08           ` Grant Likely [this message]
2011-09-27 21:08             ` Grant Likely
2011-09-27 22:13             ` Mark Brown
2011-09-27 22:13               ` Mark Brown
2011-09-28 13:04               ` Arnd Bergmann
2011-09-28 13:04                 ` Arnd Bergmann
2011-09-28 13:20                 ` Mark Brown
2011-09-28 13:20                   ` Mark Brown
2011-09-28 23:14               ` Grant Likely
2011-09-28 23:14                 ` Grant Likely
2011-09-29 11:00                 ` Mark Brown
2011-09-29 11:00                   ` Mark Brown
2011-10-03 23:02 ` Kevin Hilman
2011-10-03 23:02   ` Kevin Hilman
2011-10-04 15:52   ` Grant Likely
2011-10-04 15:52     ` Grant Likely
2011-10-04 14:51 ` G, Manjunath Kondaiah
2011-10-04 14:51   ` G, Manjunath Kondaiah
2011-10-04 14:51   ` G, Manjunath Kondaiah
2011-10-04 15:58   ` Grant Likely
2011-10-04 15:58     ` Grant Likely
2011-10-04 15:58     ` Grant Likely
2011-10-04 18:35     ` G, Manjunath Kondaiah
2011-10-04 18:35       ` G, Manjunath Kondaiah
2011-10-04 23:35       ` Grant Likely
2011-10-04 23:35         ` Grant Likely
2011-10-07  3:31         ` G, Manjunath Kondaiah
2011-10-07  3:31           ` G, Manjunath Kondaiah
2011-10-11 20:47 ` Andrew Morton
2011-10-11 20:47   ` Andrew Morton
2011-10-11 21:07   ` David Daney
2011-10-13  4:19     ` Grant Likely
2011-10-13  4:19       ` Grant Likely

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=20110927210849.GD3994@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dilee@nvidia.com \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=manjunath.gkondaiah@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.