From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: linux-imx issues with make 3.82
Date: Sun, 21 Dec 2014 16:52:41 +0000 [thread overview]
Message-ID: <1419180761.13316.61.camel@linuxfoundation.org> (raw)
Hi Otavio,
https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/133/steps/BuildImages/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/133/steps/BuildImages/logs/stdio
It seems linux-imx is continuing to fail on some autobuilders but not
others (hence I thought we'd fixed it). It seems the problem is old
kernels with make 3.82. Would you be able to apply something like the
patch in:
http://www.gossamer-threads.com/lists/linux/kernel/1263151
to linux-imx so it works with make 3.82?
Cheers,
Richard
next reply other threads:[~2014-12-21 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 16:52 Richard Purdie [this message]
2014-12-21 19:01 ` linux-imx issues with make 3.82 Otavio Salvador
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=1419180761.13316.61.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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