All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Linus Walleij <linus.walleij@stericsson.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: Defer failed gpio requests by default
Date: Tue, 10 Jul 2012 12:07:40 +0100	[thread overview]
Message-ID: <20120710110739.GD3918@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACxGe6uJUTtcmq2voo0yGQZ-OxiOK-0OEJ343qZZMDTMQc6veg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

On Mon, Jul 09, 2012 at 10:54:41PM +0100, Grant Likely wrote:

> I'm fine with this patch, but the patch that adds the twizzling of the
> dpm_list when probing needs some tweaking, and this patch must be
> applied after that one.  I'll go and reply to that patch now (and cc
> you if you're not already).

Given how many subsystems are already doing the -EPROBE_DEFER stuff it
seems like we're already at the point where the core logic needs to be
bugfixes I'm not sure it's worth holding off, any system that's hitting
this is already buggy anyway so at worst we're just shifting the bug
around.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-10 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 11:22 [PATCH] gpiolib: Defer failed gpio requests by default Mark Brown
2012-07-09 20:31 ` Linus Walleij
2012-07-09 21:54   ` Grant Likely
2012-07-10 11:07     ` Mark Brown [this message]
2012-07-17 18:20 ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2012-05-02 11:49 Mark Brown
2012-05-18  4:32 ` Grant Likely
2012-05-18  8:45   ` Mark Brown
2012-05-18 16:35   ` Alan Stern

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=20120710110739.GD3918@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.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.