From: Scott Wood <scottwood@freescale.com>
To: Kushwaha Prabhakar-B32579 <prabhakar@freescale.com>,
Dogra Raghav-B46184 <raghav@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [1/2] mpc85xx/lbc: modify suspend/resume entry sequence
Date: Wed, 23 Dec 2015 22:49:15 -0600 [thread overview]
Message-ID: <1450932555.18314.121.camel@freescale.com> (raw)
In-Reply-To: <DM2PR0301MB06702E55727D2B36887B6E2DA9E70@DM2PR0301MB0670.namprd03.prod.outlook.com>
On Wed, 2015-12-23 at 22:38 -0600, Kushwaha Prabhakar-B32579 wrote:
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Thursday, December 24, 2015 9:49 AM
> > To: Dogra Raghav-B46184 <raghav@freescale.com>
> > Cc: linuxppc-dev@lists.ozlabs.org; Kushwaha Prabhakar-B32579
> > <prabhakar@freescale.com>
> > Subject: Re: [1/2] mpc85xx/lbc: modify suspend/resume entry sequence
> >
> > On Fri, Oct 30, 2015 at 11:54:59AM +0530, Raghav Dogra wrote:
> > > /* restore lbc registers */
> > > -static int fsl_lbc_resume(struct platform_device *pdev)
> > > +static int fsl_lbc_syscore_resume(void)
> > > {
> > > - struct fsl_lbc_ctrl *ctrl = dev_get_drvdata(&pdev->dev);
> > > - struct fsl_lbc_regs __iomem *lbc = ctrl->regs;
> > > + struct fsl_lbc_ctrl *ctrl;
> > > + struct fsl_lbc_regs __iomem *lbc;
> > > +
> > > + ctrl = fsl_lbc_ctrl_dev;
> > > + if (!ctrl)
> > > + goto out;
> > > +
> > > + lbc = ctrl->regs;
> > > + if (!lbc)
> > > + goto out;
> > >
> > > if (ctrl->saved_regs) {
> > > _memcpy_toio(lbc, ctrl->saved_regs, @@ -379,7 +398,9 @@
> > static int
> > > fsl_lbc_resume(struct platform_device *pdev)
> > > kfree(ctrl->saved_regs);
> > > ctrl->saved_regs = NULL;
> > > }
> > > - return 0;
> > > +
> > > +out:
> > > + return;
> > > }
> >
> > arch/powerpc/sysdev/fsl_lbc.c:401:2: error:
> > 'return' with no value, in function returning non-void [-Werror=return
> > -type]
> >
> >
> > > #endif /* CONFIG_SUSPEND */
> > >
> > > @@ -391,20 +412,26 @@ static const struct of_device_id fsl_lbc_match[] =
> > {
> > > {},
> > > };
> > >
> > > +#ifdef CONFIG_SUSPEND
> > > +static struct syscore_ops lbc_syscore_pm_ops = {
> > > + .suspend = fsl_lbc_syscore_suspend,
> > > + .resume = fsl_lbc_syscore_resume,
> > > +};
> > > +#endif
> >
> > arch/powerpc/sysdev/fsl_lbc.c:416:2: error:
> > initialization from incompatible pointer type [-Werror]
> > arch/powerpc/sysdev/fsl_lbc.c:416:2: error:
> > (near initialization for 'lbc_syscore_pm_ops.resume') [-Werror]
> >
>
> Can you please help us with the tool-chain used for compiling.
It doesn't matter. The patch is clearly wrong based on inspection.
-Scott
next prev parent reply other threads:[~2015-12-24 4:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 6:24 [PATCH 1/2] mpc85xx/lbc: modify suspend/resume entry sequence Raghav Dogra
2015-10-30 20:03 ` Scott Wood
2015-11-02 6:12 ` Dogra Raghav
2015-11-02 23:00 ` Scott Wood
2015-11-03 5:31 ` Dogra Raghav
2015-11-03 5:39 ` Scott Wood
2015-11-03 6:09 ` Dogra Raghav
2015-11-03 6:13 ` Scott Wood
2015-11-03 6:33 ` Dogra Raghav
2015-11-03 7:36 ` Scott Wood
2015-11-03 9:12 ` Dogra Raghav
2015-12-23 21:10 ` Scott Wood
2015-12-24 4:19 ` [1/2] " Scott Wood
2015-12-24 4:38 ` Kushwaha Prabhakar
2015-12-24 4:49 ` Scott Wood [this message]
2015-12-24 5:22 ` Kushwaha Prabhakar
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=1450932555.18314.121.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=prabhakar@freescale.com \
--cc=raghav@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).