From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] ltrace: Fix build on mips
Date: Sat, 7 Sep 2019 13:21:06 +0300 [thread overview]
Message-ID: <20190907102106.GA26201@localhost> (raw)
In-Reply-To: <c74a44cc-b085-e526-eabb-bb56441a5362@gmail.com>
On Fri, Sep 06, 2019 at 05:12:24PM -0700, akuster808 wrote:
> On 9/6/19 2:25 PM, Khem Raj wrote:
> > Newer kernel UAPI headers for mips have moved these needed defines
> > around
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> warrior too?
>...
No, this is not a problem with the UAPI headers in warrior.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-09-07 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 21:25 [meta-oe][PATCH] ltrace: Fix build on mips Khem Raj
2019-09-07 0:12 ` akuster808
2019-09-07 0:17 ` Khem Raj
2019-09-07 10:21 ` Adrian Bunk [this message]
2019-09-07 14:36 ` Khem Raj
2019-09-08 13:08 ` Adrian Bunk
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=20190907102106.GA26201@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@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