From: Tony Lindgren <tony@atomide.com>
To: Pekon Gupta <pekon@ti.com>
Cc: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
avinash philip <avinashphilip@ti.com>
Subject: Re: [PATCH v4 2/3] arm: gpmc: Low power transition support
Date: Wed, 12 Jun 2013 10:38:54 -0700 [thread overview]
Message-ID: <20130612173854.GP8164@atomide.com> (raw)
In-Reply-To: <20130612170126.GI8164@atomide.com>
* Tony Lindgren <tony@atomide.com> [130612 10:08]:
> * Pekon Gupta <pekon@ti.com> [130612 04:07]:
> > From: avinash philip <avinashphilip@ti.com>
> >
> > With GPMC converted to platform driver recently, adds low power
> > transition support in driver itself.
>
> Applying the first two patches of this series into omap-for-v3.11/gpmc.
> Not taking the MTD patch, if it has dependencies to the first two
> patches please let me know and also get an ack from Artem if you
> want me to take it.
Oops, dropping the second patch in this series as it causes the
following if only omap4 is selected for example:
arch/arm/mach-omap2/built-in.o: In function `gpmc_resume':
dss-common.c:(.text+0x9a8): undefined reference to `omap3_gpmc_restore_context'
arch/arm/mach-omap2/built-in.o: In function `gpmc_suspend':
dss-common.c:(.text+0x9c8): undefined reference to `omap3_gpmc_save_context'
Can you please take a lok and fix that?
Regards,
Tony
next prev parent reply other threads:[~2013-06-12 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 11:00 [PATCH v4 0/3] suspend/resume support for OMAP nand driver Pekon Gupta
2013-06-12 11:00 ` [PATCH v4 1/3] arm: gpmc: Converts GPMC driver to pm_runtime capable Pekon Gupta
2013-06-12 11:00 ` [PATCH v4 2/3] arm: gpmc: Low power transition support Pekon Gupta
2013-06-12 17:01 ` Tony Lindgren
2013-06-12 17:38 ` Tony Lindgren [this message]
2013-06-12 11:00 ` [PATCH v4 3/3] mtd: devices: elm: " Pekon Gupta
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=20130612173854.GP8164@atomide.com \
--to=tony@atomide.com \
--cc=avinashphilip@ti.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@ti.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).