From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Subject: Re: cron job: media_tree daily build: ABI WARNING
Date: Sun, 20 Mar 2016 10:54:09 +0100 [thread overview]
Message-ID: <56EE7341.1080302@xs4all.nl> (raw)
In-Reply-To: <20160320040141.4F8CB182E7D@tschai.lan>
On 03/20/2016 05:01 AM, Hans Verkuil wrote:
> ABI WARNING: change for arm-at91
> ABI WARNING: change for arm-davinci
> ABI WARNING: change for arm-exynos
> ABI WARNING: change for arm-mx
> ABI WARNING: change for arm-omap
> ABI WARNING: change for arm-omap1
> ABI WARNING: change for arm-pxa
> ABI WARNING: change for blackfin-bf561
> ABI WARNING: change for i686
> ABI WARNING: change for m32r
> ABI WARNING: change for mips
> ABI WARNING: change for powerpc64
> ABI WARNING: change for sh
> ABI WARNING: change for x86_64
Ignore the ABI warning: it's my fault caused by different 'sort' results
due to a different LC_ALL setting.
Should now be fixed.
Regards,
Hans
next prev parent reply other threads:[~2016-03-20 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 4:01 cron job: media_tree daily build: ABI WARNING Hans Verkuil
2016-03-20 9:54 ` Hans Verkuil [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-30 1:51 Hans Verkuil
2018-02-22 4:43 Hans Verkuil
2018-02-21 4:43 Hans Verkuil
2018-02-20 4:44 Hans Verkuil
2018-02-20 12:51 ` Hans Verkuil
2018-02-17 4:50 Hans Verkuil
2018-02-17 9:07 ` Hans Verkuil
2017-04-16 4:19 Hans Verkuil
2016-09-13 3:07 Hans Verkuil
2015-03-24 3:46 Hans Verkuil
2015-02-28 3:45 Hans Verkuil
2015-02-20 3:45 Hans Verkuil
2015-02-19 3:44 Hans Verkuil
2015-02-18 3:45 Hans Verkuil
2015-02-17 3:44 Hans Verkuil
2014-12-06 3:43 Hans Verkuil
2014-07-22 6:26 Hans Verkuil
2014-07-18 2:45 Hans Verkuil
2014-05-26 2:43 Hans Verkuil
2013-11-13 3:32 Hans Verkuil
2013-11-13 7:26 ` Hans Verkuil
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=56EE7341.1080302@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).