All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved
Date: Sat, 06 Apr 2013 10:30:36 -0700	[thread overview]
Message-ID: <51605BBC.6080009@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKpN2uNMJy5Fi0FN=1rFS=6UZ1t=4wQVUbrnV+sQV_xyUA@mail.gmail.com>

On 04/06/2013 10:13 AM, Otavio Salvador wrote:
> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi Otavio,
>>
>>
>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>
>>> The SabreLITE machine is now supported using the Boundary Devices
>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>> overrides of this recipe.
>>>
>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>> ---
>>>    .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>    .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>> --------------------
>>>    recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>    3 files changed, 7748 deletions(-)
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>
>>
>> Are there dependencies on this patch?
>>
>> It didn't apply cleanly based on Master+patch 1 of the series.
>
> My tree looks like:
>
> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
> 680c6a3 gst-plugins-gl: Avoid leaking memory
>
Thanks Otavio,

It looks like I had some leftover stuff in my local tree and
'repo init -b master' didn't fix it...





  reply	other threads:[~2013-04-06 17:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 16:30 [meta-fsl-arm][PATCH 1/2] imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra Otavio Salvador
2013-04-06 16:30 ` [meta-fsl-arm-extra][PATCH 1/3] linux-boundary: Add recipe for Boundary Devices kernel Otavio Salvador
2013-04-06 16:30 ` [meta-fsl-arm-extra][PATCH 2/3] imx6qsabrelite: Add Boundary Devices SabreLITE machine definition Otavio Salvador
2013-04-06 16:30 ` [meta-fsl-arm-extra][PATCH 3/3] nitrogen6x: Change machine to use linux-boundary kernel Otavio Salvador
     [not found] ` <1365265828-28655-4-git-send-email-otavio@ossystems.com.br>
2013-04-06 17:08   ` [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved Eric Nelson
2013-04-06 17:13     ` Otavio Salvador
2013-04-06 17:30       ` Eric Nelson [this message]
2013-04-06 21:07         ` Otavio Salvador
2013-04-08 15:01           ` Eric Nelson
2013-04-08 16:04             ` Otavio Salvador
2013-10-16 16:27   ` Eric Nelson
2013-10-16 17:04     ` Otavio Salvador
2013-10-16 20:10       ` Eric Nelson
2013-10-16 20:21         ` Otavio Salvador
2013-10-16 20:24           ` Eric Nelson
2013-10-16 20:30             ` Otavio Salvador
2013-10-16 20:50               ` Eric Nelson

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=51605BBC.6080009@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.