From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Build regressions/improvements in v4.1
Date: Mon, 22 Jun 2015 22:18:57 +0100 [thread overview]
Message-ID: <20150622211857.GY7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAMuHMdXprKyxirhUZBzNV97oxymcMqeugKixTEC8ojcMq3EeDw@mail.gmail.com>
On Mon, Jun 22, 2015 at 10:52:13PM +0200, Geert Uytterhoeven wrote:
> On Mon, Jun 22, 2015 at 10:48 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > JFYI, when comparing v4.1[1] to v4.1-rc8[3], the summaries are:
> > - build errors: +44/-7
>
> + /home/kisskb/slave/src/arch/arm/mm/dump.c: error:
> 'L_PTE_MT_BUFFERABLE' undeclared here (not in a function): => 81:10
> + /home/kisskb/slave/src/arch/arm/mm/dump.c: error:
> 'L_PTE_MT_DEV_CACHED' undeclared here (not in a function): => 117:10
> + /home/kisskb/slave/src/arch/arm/mm/dump.c: error:
> 'L_PTE_MT_DEV_NONSHARED' undeclared here (not in a function): =>
> 108:10
I'm rather ignoring this because I don't see these errors here. This
is one of the problems of just throwing out build reports. With zero
information such as a configuration or a method on how to cause the
errors, it's pretty much worthless to post errors.
Folk who do build testing need to be smarter, and consider what it's
like to be on the receiving end of their report emails...
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-22 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435006096-12470-1-git-send-email-geert@linux-m68k.org>
2015-06-22 20:52 ` Build regressions/improvements in v4.1 Geert Uytterhoeven
2015-06-22 21:18 ` Russell King - ARM Linux [this message]
2015-06-23 7:50 ` Geert Uytterhoeven
2015-06-25 9:18 ` Russell King - ARM Linux
2015-06-25 9:30 ` Russell King - ARM Linux
2015-06-25 9:34 ` Russell King - ARM Linux
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=20150622211857.GY7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).