From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH 0/2] linux-boundary_3.10.17 kernel bumps
Date: Sat, 01 Nov 2014 11:06:14 -0700 [thread overview]
Message-ID: <54552116.6080704@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKqkQRVPCd7TALibDz=Sqka_oDPgF6+sCYPTgvgXeKpuog@mail.gmail.com>
On 11/01/2014 10:50 AM, Otavio Salvador wrote:
> Hello Eric,
>
> On Fri, Oct 31, 2014 at 7:33 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> These two patches bring the linux-boundary_3.10.17 up to date with
>> the latest head of our boundary-imx_3.10.17_1.0.1_ga branch (patch 1)
>> and then switch to the new boundary-imx_3.10.17_1.0.2_ga branch
>> to keep in sync with the 3.10.17_1.0.2 Freescale release (patch 2).
>>
>> The second patch should be applied along with the userspace updates
>> from Freescale.
>
> Yes; I am queueing it in master-next for test and will merge it
> together with the 1.0.2 branch.
>
>> The first patch should be applied to dizzy, master, and master-next.
>
> Done.
>
Thanks Otavio
prev parent reply other threads:[~2014-11-01 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:33 [meta-fsl-arm-extra][PATCH 0/2] linux-boundary_3.10.17 kernel bumps Eric Nelson
2014-10-31 21:33 ` [meta-fsl-arm-extra][PATCH 1/2] linux-boundary (3.10.17): Bump SRCREV to 9f710dad Eric Nelson
2014-10-31 21:33 ` [meta-fsl-arm-extra][PATCH 2/2] linux-boundary: Upgrade to 3.10.17_1.0.2 patch release (commit f7a1e187) Eric Nelson
2014-11-01 17:50 ` [meta-fsl-arm-extra][PATCH 0/2] linux-boundary_3.10.17 kernel bumps Otavio Salvador
2014-11-01 18:06 ` Eric Nelson [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=54552116.6080704@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.