From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] sstate: Avoid indirect bison/flex-native dependencies
Date: Tue, 10 Apr 2018 17:36:54 +0100 [thread overview]
Message-ID: <1523378214.2942.158.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180410143311.GD3228@denix.org>
On Tue, 2018-04-10 at 10:33 -0400, Denys Dmytriyenko wrote:
> Richard,
>
> Was this patch ever merged? I don't see it in master - were there any
> problems
> or concerns?
There was some kind of failure in testing on the autobuilder which made
me abandon it, I can't remember what it was though :(
Cheers,
Richard
next prev parent reply other threads:[~2018-04-10 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 17:01 [PATCH 1/4] perf: Add missing bison-native and flex-native dependencies Richard Purdie
2018-01-11 17:01 ` [PATCH 2/4] at: Add missing bison-native dependency Richard Purdie
2018-01-11 17:01 ` [PATCH 3/4] gcc: Add missing flex-native dependency Richard Purdie
2018-01-11 17:01 ` [PATCH 4/4] sstate: Avoid indirect bison/flex-native dependencies Richard Purdie
2018-04-10 14:33 ` Denys Dmytriyenko
2018-04-10 16:36 ` Richard Purdie [this message]
2018-04-10 16:48 ` Denys Dmytriyenko
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=1523378214.2942.158.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=denis@denix.org \
--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 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.