From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] linux-yocto: update beaglebone, mpc8315e and edgerouter to 3.19
Date: Fri, 5 Jun 2015 11:13:32 -0400 [thread overview]
Message-ID: <5571BC9C.5030704@windriver.com> (raw)
In-Reply-To: <CAJTo0LYE8Oe6=aK0GekB+vb0TPZVZLCAtNUjecD9BZv3EZWEFQ@mail.gmail.com>
On 2015-06-05 11:07 AM, Burton, Ross wrote:
>
> On 5 June 2015 at 05:13, Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>> wrote:
>
> Bumping the linux-yocto SRCREVs to integrate fixes for the h/w reference
> BSPs to the 3.19 kernel.
>
>
> edgerouter fails for me:
>
It's Kevin you should be cc'ing .. I'm just the guy that merges
these ones :)
Kevin did fix this though .. I wonder if I did drop a patch, so I'll
double check (maybe I was the right guy to cc' ')
Bruce
> |
> /data/poky-master/tmp/work-shared/edgerouter/kernel-source/fs/aufs/i_op.c:
> In function 'au_pin_hdir_set_owner':
> |
> /data/poky-master/tmp/work-shared/edgerouter/kernel-source/fs/aufs/i_op.c:445:28:
> error: 'struct mutex' has no member named 'owner'
> | p->hdir->hi_inode->i_mutex.owner = task;
> | ^
> | LD drivers/idle/built-in.o
> | CC fs/aufs/i_op_del.o
> | LD drivers/i2c/busses/built-in.o
> | CC drivers/base/module.o
> | LD drivers/i2c/muxes/built-in.o
> |
> /data/poky-master/tmp/work-shared/edgerouter/kernel-source/scripts/Makefile.build:257:
> recipe for target 'fs/aufs/i_op.o' failed
> | make[4]: *** [fs/aufs/i_op.o] Error 1
>
> Ross
next prev parent reply other threads:[~2015-06-05 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 4:13 [PATCH 0/1] linux-yocto/3.19: update reference BSPs to 3.19 Bruce Ashfield
2015-06-05 4:13 ` [PATCH 1/1] linux-yocto: update beaglebone, mpc8315e and edgerouter " Bruce Ashfield
2015-06-05 15:07 ` Burton, Ross
2015-06-05 15:13 ` Bruce Ashfield [this message]
2015-06-05 15:22 ` Bruce Ashfield
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=5571BC9C.5030704@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox