From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] linux-libc-headers: ptrace.h: remove ptrace_peeksiginfo_args
Date: Mon, 26 Aug 2013 12:03:13 +0100 [thread overview]
Message-ID: <1377514993.26773.42.camel@ted> (raw)
In-Reply-To: <521AD8F8.10807@windriver.com>
On Mon, 2013-08-26 at 00:26 -0400, Bruce Ashfield wrote:
> On 13-08-26 12:08 AM, Saul Wold wrote:
> Thanks! And honestly, I didn't leave out the upstream status on purpose
> this time .. like I said, it just isn't in my workflow, since I normally
> seek and destroy them!
>
> I'm pretty sure I can't convince the kernel guys to not export that
> structure, but I can try. Otherwise, it can have the "dirty hack" upstream
> status.
>
> >
> > I will put this in MUT so we can move forward tonight.
>
> Fingers crossed, my builds are working here.
Things failed badly on the autobuilder since we dropped the command
length patch and it was still needed. I've updated it against 3.10,
confirmed it worked on the autobuilder and then merged things.
Cheers,
Richard
next prev parent reply other threads:[~2013-08-26 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 3:25 linux-libc-headers: fix 3.10 build issues Bruce Ashfield
2013-08-26 3:25 ` [PATCH] linux-libc-headers: ptrace.h: remove ptrace_peeksiginfo_args Bruce Ashfield
2013-08-26 4:08 ` Saul Wold
2013-08-26 4:26 ` Bruce Ashfield
2013-08-26 11:03 ` Richard Purdie [this message]
2013-08-26 12:39 ` Bruce Ashfield
2013-08-26 13:18 ` Richard Purdie
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=1377514993.26773.42.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox