public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Samuel Ortiz <sameo@linux•intel.com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Arnd Hannemann <arnd@arndnet•de>,
	Paul Mundt <lethal@linux-sh•org>
Subject: linux-next: manual merge of the mfd tree with the sh tree
Date: Fri, 17 Sep 2010 12:05:48 +1000	[thread overview]
Message-ID: <20100917120548.5dc723ec.sfr@canb.auug.org.au> (raw)

Hi Samuel,

Today's linux-next merge of the mfd tree got a conflict in
drivers/mfd/sh_mobile_sdhi.c between commit
25ab998e2eff46d2e6ede80c9fc02a349fa005a3 ("mfd: Fix up section mismatches
in SH SDHI") from the sh tree and commit
6d1b291f5f2728547a8d681b46657ed9528145bf ("mfd: Allow the platform to
specify the sh_mobile_sdhi get_cd handler") from the mfd tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc drivers/mfd/sh_mobile_sdhi.c
index 49b4d06,9d43316..0000000
--- a/drivers/mfd/sh_mobile_sdhi.c
+++ b/drivers/mfd/sh_mobile_sdhi.c
@@@ -65,7 -65,18 +65,18 @@@ static void sh_mobile_sdhi_set_pwr(stru
  		p->set_pwr(pdev, state);
  }
  
+ static int sh_mobile_sdhi_get_cd(struct platform_device *tmio)
+ {
+ 	struct platform_device *pdev = to_platform_device(tmio->dev.parent);
+ 	struct sh_mobile_sdhi_info *p = pdev->dev.platform_data;
+ 
+ 	if (p && p->get_cd)
+ 		return p->get_cd(pdev);
+ 	else
+ 		return -ENOSYS;
+ }
+ 
 -static int __init sh_mobile_sdhi_probe(struct platform_device *pdev)
 +static int __devinit sh_mobile_sdhi_probe(struct platform_device *pdev)
  {
  	struct sh_mobile_sdhi *priv;
  	struct tmio_mmc_data *mmc_data;

                 reply	other threads:[~2010-09-17  2:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100917120548.5dc723ec.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arnd@arndnet$(echo .)de \
    --cc=lethal@linux-sh$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sameo@linux$(echo .)intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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