All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] dm: core: allow drivers to refuse to bind
Date: Wed, 4 May 2016 14:02:24 -0600	[thread overview]
Message-ID: <572A5550.5040107@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ2QQ28mhv0d_DqVQxyN+899xiP23coYo9ReTQFCYkCV8Q@mail.gmail.com>

On 05/04/2016 01:48 PM, Simon Glass wrote:
> +Tom Rini
>
> Hi Stephen,
>
> On 4 May 2016 at 13:46, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 05/04/2016 01:31 PM, Simon Glass wrote:
>>>
>>> Hi Stephen,
>>>
>>> On 4 May 2016 at 12:57, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>>
>>>> On 04/19/2016 04:19 PM, Stephen Warren wrote:
>>>>>
>>>>>
>>>>> From: Stephen Warren <swarren@nvidia.com>
>>>>>
>>>>> In some cases, drivers may not want to bind to a device. Allow bind() to
>>>>> return -ENODEV in this case, and don't treat this as an error. This can
>>>>> be useful in situations where some information source other than the DT
>>>>> node's main status property indicates whether the device should be
>>>>> enabled, for example other DT properties might indicate this, or the
>>>>> driver might query non-DT sources such as system fuses or a version
>>>>> number
>>>>> register.
>>>>
>>>>
>>>>
>>>> Simon, this series is assigned to you in patchwork. Are you the right
>>>> person
>>>> to apply it?
>>>
>>>
>>> Yes. but not for this release, right?
>>
>>
>> Patch 2 in the series (which depends on this patch) fixes a bug for Tegra
>> boards with LCD panels. Admittedly it appears to be only cosmetic (an error
>> message is printed at boot), but "it's a bug" seems to satisfy the
>> requirement to apply it for this release.
>
> Sorry, I didn't know that. Given the core nature of this patch I would
> rather wait, and apply it next week. Let me know if you disagree.

I suppose that it's been broken long enough that another release won't 
matter.

Was my explanation of the bug in the description of patch 2/2 not clear 
in some way?

  reply	other threads:[~2016-05-04 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 22:19 [U-Boot] [PATCH 1/2] dm: core: allow drivers to refuse to bind Stephen Warren
2016-04-19 22:19 ` [U-Boot] [PATCH 2/2] video: tegra: refuse to bind to disabled dcs Stephen Warren
2016-04-20 12:49   ` Thierry Reding
2016-04-20 13:16   ` Simon Glass
2016-05-07 19:03     ` Simon Glass
2016-04-20 14:42 ` [U-Boot] [PATCH 1/2] dm: core: allow drivers to refuse to bind Simon Glass
2016-05-04 18:57 ` Stephen Warren
2016-05-04 19:31   ` Simon Glass
2016-05-04 19:46     ` Stephen Warren
2016-05-04 19:48       ` Simon Glass
2016-05-04 20:02         ` Stephen Warren [this message]
2016-05-04 20:09           ` Simon Glass
2016-05-07 19:02             ` Simon Glass

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=572A5550.5040107@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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.