All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH] [meta-ppc-fsl] on master, move linux patches under newly created files subdirectory
Date: Mon, 07 Jan 2013 15:40:42 -0500	[thread overview]
Message-ID: <50EB32CA.90203@mindchasers.com> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A818C66@039-SN1MPN1-002.039d.mgd.msft.net>

On 01/07/2013 03:14 PM, McClintock Matthew-B29882 wrote:
> On Mon, Jan 7, 2013 at 9:39 AM, Bob Cochran <yocto@mindchasers.com> wrote:
>> As I reported back on 11/27, I get linux-qoriq-sdk-headers build errors with
>> the linux patch files located in meta-fsl-ppc/recipes-kernel/linux.
>> Therefore, I created a files subdirectioy and moved the patch files under
>> there.
>
> This is in master-next...
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/commit/?h=master-next&id=88c9c66b588346143a2277f119f78bb2e82e3db3
>
> I'm sorry I've not tested and pushed to master but I've had serious
> issues with our build machines and testing the builds, between that
> and holiday vacation. Progress is being made again.
>
> -M
>
>

Thanks Matthew.  I'm glad to hear master will be moving along again.

I have what seems like more than one problem getting Master to make it 
through the init sequence on my p1010rdb.  I'm working it in the 
margins, and I'll send something out if I discover something meaningful.








      reply	other threads:[~2013-01-07 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 15:39 [PATCH] [meta-ppc-fsl] on master, move linux patches under newly created files subdirectory Bob Cochran
2013-01-07 17:06 ` Otavio Salvador
2013-01-07 20:14 ` McClintock Matthew-B29882
2013-01-07 20:40   ` Bob Cochran [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=50EB32CA.90203@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=B29882@freescale.com \
    --cc=meta-freescale@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.