All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] dm: Protect device_unbind() with CONFIG_DM_DEVICE_REMOVE
Date: Thu, 5 Mar 2015 22:00:23 +0100	[thread overview]
Message-ID: <201503052200.23878.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ00qgjvjYaoib2VtG_0uJaWieaSmxDhNxju9Nz2Egc7vg@mail.gmail.com>

On Friday, February 20, 2015 at 08:31:20 PM, Simon Glass wrote:
> Hi Marek,

Hi Simon,

things are starting to settle down a bit finally.

[...]

> > In case I base those patches on v2015.04-rc1 , I don't see this error,
> > but in case I base those patches on top of v2015.04-rc2, I do see it. Do
> > you have any hint which changes between these two points can cause this
> > breakage please ?
> 
> It is probably the Kconfig conversion - now there will be extra options
> enabled.
> 
> > Also, about the Kconfig, shall I introduce the entries for those two
> > drivers or what is the plan here ? I would like to get these patches
> > into the current release.
> 
> Yes please.

Should be all taken care of now :)

Best regards,
Marek Vasut

  reply	other threads:[~2015-03-05 21:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 21:36 [U-Boot] [PATCH 1/2] dm: Protect device_unbind() with CONFIG_DM_DEVICE_REMOVE Marek Vasut
2015-02-18 21:36 ` [U-Boot] [PATCH 2/2] arm: socfpga: Enable DM for Cadence and DW SPI Marek Vasut
2015-02-19  1:07   ` Simon Glass
2015-02-19  9:44     ` Marek Vasut
2015-02-19 18:28       ` Simon Glass
2015-03-05 21:00         ` Marek Vasut
2015-02-19  1:06 ` [U-Boot] [PATCH 1/2] dm: Protect device_unbind() with CONFIG_DM_DEVICE_REMOVE Simon Glass
2015-02-19  8:50   ` Marek Vasut
2015-02-19 14:29     ` Simon Glass
2015-02-19 14:34       ` Marek Vasut
2015-02-19 15:24         ` Simon Glass
2015-02-19 18:19           ` Marek Vasut
2015-02-20 19:31             ` Simon Glass
2015-03-05 21:00               ` Marek Vasut [this message]
2015-02-19 18:27   ` 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=201503052200.23878.marex@denx.de \
    --to=marex@denx.de \
    --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.