From: "Eric Bénard" <eric@eukrea.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Mahadevan Mahesh-R9AADQ <r9aadq@freescale.com>
Subject: Re: [fsl-community-bsp-platform][PATCH] linux-imx (2.6.35): mxs and mx5: Update to latest from FSL GIT
Date: Fri, 5 Apr 2013 08:46:07 +0200 [thread overview]
Message-ID: <20130405084607.2250bb0f@e6520eb> (raw)
In-Reply-To: <CAP9ODKoPJxbdZf7njT32cL1suiEC=Da9FPRKLDeucoxSU=Usiw@mail.gmail.com>
Hi Otavio,
Le Thu, 4 Apr 2013 18:16:11 -0300,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> On Thu, Apr 4, 2013 at 6:02 PM, Mahadevan Mahesh-R9AADQ
> <r9aadq@freescale.com> wrote:
> > Merge has already been done. Future releases for MX53 and MX28 will be based off this branch.
> >
> > Same branch for both.
>
>
> We are very close of branching to 1.4 release and I am not comfortable
> in changing the kernel version to a new branch that close. We're using
> the "oficial" BSP release for now and I'd prefer to change it after we
> start 1.5 development so we can get a good test coverage.
>
We still have 20 days before Yocto 1.4's release to validate these
changes so if the official Freescale maintainers say this kernel is the
one to use for i.MX53 and i.MX28 I would trust him and I think it
would be great to take the opportunity to release 1.4 as a really up to
date BSP for mature products like i.MX28 and i.MX53.
When looking at the commit log of this branch we can see that it
contains many fixes so the risk of regression is quite limited.
Best regards,
Eric
next prev parent reply other threads:[~2013-04-05 6:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 19:50 [fsl-community-bsp-platform][PATCH] linux-imx (2.6.35): mxs and mx5: Update to latest from FSL GIT Mahesh Mahadevan
2013-04-04 20:19 ` Otavio Salvador
2013-04-04 21:02 ` Mahadevan Mahesh-R9AADQ
2013-04-04 21:16 ` Otavio Salvador
2013-04-05 6:46 ` Eric Bénard [this message]
2013-04-05 12:34 ` Otavio Salvador
2013-04-05 12:48 ` Eric Bénard
2013-04-05 12:51 ` Otavio Salvador
2013-04-05 13:14 ` Eric Bénard
2013-04-05 16:50 ` Fabio Estevam
2013-04-05 17:26 ` Mahadevan Mahesh-R9AADQ
2013-04-05 17:37 ` Otavio Salvador
2013-04-05 17:38 ` Otavio Salvador
2013-04-25 19:45 ` Mahadevan Mahesh-R9AADQ
2013-04-25 20:21 ` Otavio Salvador
2013-04-25 20:52 ` Mahadevan Mahesh-R9AADQ
-- strict thread matches above, loose matches on Subject: below --
2013-04-29 13:43 Mahesh Mahadevan
2013-04-29 13:50 ` Fabio Estevam
2013-04-29 13:58 Mahesh Mahadevan
2013-04-29 14:05 ` Fabio Estevam
2013-04-29 14:15 ` Mahadevan Mahesh-R9AADQ
2013-04-29 14:29 ` Daiane Angolini
2013-04-29 14:58 ` Otavio Salvador
2013-04-29 14:57 ` Otavio Salvador
2013-04-29 15:01 ` Fabio Estevam
2013-04-29 15:03 ` Otavio Salvador
2013-04-29 15:01 ` Otavio Salvador
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=20130405084607.2250bb0f@e6520eb \
--to=eric@eukrea.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=r9aadq@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 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.