From: Yuantian Tang <Yuantian.Tang@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mpc85xx: clean up the old deep sleep framework
Date: Thu, 18 Dec 2014 02:43:28 +0000 [thread overview]
Message-ID: <DM2PR03MB574735C0827704B24EAD397FA6A0@DM2PR03MB574.namprd03.prod.outlook.com> (raw)
In-Reply-To: <54923C75.7060808@freescale.com>
Hello York,
The following 3 patches, which are independent to each other, should be applied first before this one get applied.
You can apply these 4 patches in the order I sent them.
1. mpc85xx/t102xrdb: convert deep sleep to generic board interface
http://patchwork.ozlabs.org/patch/422189/
2. mpc85xx/t1040qds: convert deep sleep to generic board interface
http://patchwork.ozlabs.org/patch/422451/
3. mpc85xx/t102xqds: convert deep sleep to generic board interface
http://patchwork.ozlabs.org/patch/422447/
Thanks,
Yuantian
> -----Original Message-----
> From: York Sun [mailto:yorksun at freescale.com]
> Sent: Thursday, December 18, 2014 10:31 AM
> To: Tang Yuantian-B29983
> Cc: u-boot at lists.denx.de
> Subject: Re: [PATCH] mpc85xx: clean up the old deep sleep framework
>
> On 12/17/2014 06:26 PM, Tang Yuantian wrote:
> > All the boards that support deep sleep feature are converted to deep
> > sleep generic board interface. The old interface which support
> > non-generic board is not used anymore. So clean it up.
> >
> > Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
> > ---
>
> I know for sure we have some patches pending. It would be helpful if you list all
> the dependency so I won't apply this one first. It will be a good habit for all future
> patches.
>
> York
>
next prev parent reply other threads:[~2014-12-18 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 2:26 [U-Boot] [PATCH] mpc85xx: clean up the old deep sleep framework Tang Yuantian
2014-12-18 2:31 ` York Sun
2014-12-18 2:43 ` Yuantian Tang [this message]
2014-12-18 2:56 ` York Sun
2015-01-23 0:35 ` York Sun
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=DM2PR03MB574735C0827704B24EAD397FA6A0@DM2PR03MB574.namprd03.prod.outlook.com \
--to=yuantian.tang@freescale.com \
--cc=u-boot@lists.denx.de \
/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.