All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Kevin Hilman <khilman@linaro.org>,
	Lee Jones <lee.jones@linaro.org>,
	Jingoo Han <jg1.han@samsung.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 1/5] mfd: asic3: Remove .set_pwr() callback
Date: Fri, 06 Sep 2013 12:38:44 +0100	[thread overview]
Message-ID: <86wqmurxh7.fsf@void.printf.net> (raw)
In-Reply-To: <5649106.WzMa2Sr8sS@avalon> (Laurent Pinchart's message of "Thu, 29 Aug 2013 16:59:11 +0200")

Hi,

On Thu, Aug 29 2013, Laurent Pinchart wrote:
>> Any progress on this?  linux-next builds are still failing for the
>> following defconfigs because of this removal:
>
> Chris, could you please drop 3af9d15 "mmc: tmio-mmc: Remove .set_pwr() 
> callback from platform data" from your tree or revert it ?

Sorry for the delay.  I decided to revert instead of rebase, so I've
pushed a revert to mmc-next now.  (I haven't sent mmc-next to mainline
yet.)

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>

      reply	other threads:[~2013-09-06 11:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  5:52 [PATCH 1/5] mfd: asic3: Remove .set_pwr() callback Jingoo Han
2013-08-28  5:54 ` [PATCH 2/5] mfd: t7l66xb: " Jingoo Han
2013-08-28  5:54 ` [PATCH 3/5] mfd: tc6387xb: " Jingoo Han
2013-08-28  5:54 ` [PATCH 4/5] mfd: tc6393xb: " Jingoo Han
2013-08-28  5:55 ` [PATCH 5/5] mfd: tmio_core: Remove tmio_core_mmc_pwr() Jingoo Han
2013-08-28  6:27 ` [PATCH 1/5] mfd: asic3: Remove .set_pwr() callback Jingoo Han
2013-08-28  7:37   ` Lee Jones
2013-08-28  7:36 ` Laurent Pinchart
2013-08-28  7:41   ` Lee Jones
2013-08-28  7:51     ` Laurent Pinchart
2013-08-29 14:42       ` Kevin Hilman
2013-08-29 14:59         ` Laurent Pinchart
2013-09-06 11:38           ` Chris Ball [this message]

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=86wqmurxh7.fsf@void.printf.net \
    --to=cjb@laptop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=jg1.han@samsung.com \
    --cc=khilman@linaro.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sameo@linux.intel.com \
    /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.