From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/2] meta-yocto-bsp: enable the jffs2 for mpc8315e-rdb board
Date: Fri, 13 Jun 2014 15:55:19 +0100 [thread overview]
Message-ID: <1402671319.12440.491.camel@ted> (raw)
In-Reply-To: <539AFCD9.70307@windriver.com>
On Fri, 2014-06-13 at 09:30 -0400, Bruce Ashfield wrote:
> On 14-06-13 12:39 AM, Kevin Hao wrote:
> > Hi,
> >
> > This tries to enable the jffs2 support for the mpc8315e-rdb board. I have
> > tested the jffs2 with the following steps and it worked perfectly.
>
> The other point to add on this review/patch series, is that for it
> to fully work out of the box, it needs a merge of some kernel patches
> that Kevin sent to linux-yocto a couple of days ago.
>
> To make sure that things are coordinated, I can queue this series and
> send it along with my kernel SRCREV updates to include those patches.
>
> Obviously, I won't queue it until Kevin udpates README.hardware and
> sends a quick v2 of the changes.
>
> Does that sound acceptable to everyone ?
Sounds good to me.
Cheers,
Richard
prev parent reply other threads:[~2014-06-13 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 4:39 [PATCH 0/2] meta-yocto-bsp: enable the jffs2 for mpc8315e-rdb board Kevin Hao
2014-06-13 4:39 ` [PATCH 1/2] mpc8315e-rdb: bump to linux-yocto 3.14 Kevin Hao
2014-06-13 4:39 ` [PATCH 2/2] mpc8315e-rdb: add the jffs2 image support Kevin Hao
2014-06-13 7:04 ` [PATCH 0/2] meta-yocto-bsp: enable the jffs2 for mpc8315e-rdb board Richard Purdie
2014-06-13 13:25 ` Bruce Ashfield
2014-06-14 0:32 ` Kevin Hao
2014-06-13 13:30 ` Bruce Ashfield
2014-06-13 14:55 ` Richard Purdie [this message]
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=1402671319.12440.491.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.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 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.