From: Denys Dmytriyenko <denis@denix.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [meta-ti] massive fallout after updates / was (no subject)
Date: Thu, 21 Jun 2012 20:24:38 -0400 [thread overview]
Message-ID: <20120622002438.GE30753@denix.org> (raw)
In-Reply-To: <CALbNGRQ5CBSDS8zPnkem59mOjzAGDy8FHZifU_g5f9z59yOybg@mail.gmail.com>
On Fri, Jun 22, 2012 at 01:34:54AM +0200, Andreas Müller wrote:
> On Fri, Jun 22, 2012 at 1:02 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> No need to understand everything: By removing require linux-tools.inc
> (the fastest patch I ever had :) I can now build again.
>
> @layer maintainers: removing
>
> require linux-tools.inc
>
> should be taken into consideration
Thanks!
--
Denys
prev parent reply other threads:[~2012-06-22 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 22:11 massive fallout after updates / was (no subject) Andreas Müller
2012-06-21 23:02 ` [meta-ti] " Denys Dmytriyenko
2012-06-21 23:34 ` Andreas Müller
2012-06-22 0:24 ` Denys Dmytriyenko [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=20120622002438.GE30753@denix.org \
--to=denis@denix.org \
--cc=meta-ti@yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=schnitzeltony@googlemail.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