SUPERH platform development
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: ecovec: fixup compile error on sdhi
Date: Wed, 25 Sep 2013 00:59:22 +0000	[thread overview]
Message-ID: <86pprxd8d1.fsf@void.printf.net> (raw)
In-Reply-To: <87li2mr4dw.wl%kuninori.morimoto.gx@renesas.com>

Hi,

On Wed, Sep 25 2013, Simon Horman wrote:
> [ Cc Chris Ball ]
>
> On Tue, Sep 24, 2013 at 01:49:19AM -0700, Kuninori Morimoto wrote:
>> afa2c9407f8908e2269b243773cbb0997c553804
>> (sh: ecovec24: Use MMC/SDHI CD and RO GPIO)
>> added .tmio_flags = TMIO_MMC_USE_GPIO_CD
>> on sh_mobile_sdhi_info, but it needs
>> <linux/mfd/tmio.h> header.
>> This patch adds it
>> 
>> Reported-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
>> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>> ---
>> Simon, Paul, Magnus
>> 
>>        This patch is for SH, but Paul can pick up it ?
>>        Or Simon can ? I'm not sure...
>
> I don't believe Paul is actively working on this code at this time.
> While I am happy to pick this up I don't have an obvious
> avenue to push it upstream.
>
> Chris has previously taken MMCIF/SDHI related patches to this file
> (and only this file) through his tree. Chris, would you consider
> taking this one once it has been reviewed?

Looks like I (via mmc-next) am responsible for merging the commit
that broke it, so I'm happy to merge the fix with an ACK.  Thanks.

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

  parent reply	other threads:[~2013-09-25  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  8:49 [PATCH] sh: ecovec: fixup compile error on sdhi Kuninori Morimoto
2013-09-24  9:35 ` Laurent Pinchart
2013-09-25  0:50 ` Simon Horman
2013-09-25  0:59 ` Chris Ball [this message]
2013-09-25  1:36 ` Simon Horman

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=86pprxd8d1.fsf@void.printf.net \
    --to=cjb@laptop.org \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox