From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v7 1/2] drivers: base: add support for registering notifier about deferred probe
Date: Wed, 13 Apr 2016 07:12:54 -0700 [thread overview]
Message-ID: <20160413141254.GB12749@kroah.com> (raw)
In-Reply-To: <1460540160-18762-2-git-send-email-m.szyprowski@samsung.com>
On Wed, Apr 13, 2016 at 11:35:59AM +0200, Marek Szyprowski wrote:
> This patch adds code which allow other subsystems get a notification
> when deferred probe has been triggered. This way one can retry some
> actions, which earlier failed with -EPROBE_DEFER error code.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Why would some other subsystem want/care about this? You aren't telling
them what device was deferred, and you don't need to as the bus itself
already knows this information as it did the deferring!
confused,
greg k-h
next prev parent reply other threads:[~2016-04-13 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 9:35 [PATCH v7 0/2] AMBA: add complete support for power domains Marek Szyprowski
2016-04-13 9:35 ` [PATCH v7 1/2] drivers: base: add support for registering notifier about deferred probe Marek Szyprowski
2016-04-13 14:12 ` Greg Kroah-Hartman [this message]
2016-04-14 7:36 ` Marek Szyprowski
2016-04-14 8:40 ` Russell King - ARM Linux
2016-04-14 21:17 ` Greg Kroah-Hartman
2016-04-14 21:33 ` Russell King - ARM Linux
2016-04-14 21:51 ` Greg Kroah-Hartman
2016-04-13 9:36 ` [PATCH v7 2/2] drivers: amba: properly handle devices with power domains Marek Szyprowski
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=20160413141254.GB12749@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=ulf.hansson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®