From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: Build regressions/improvements in v3.10-rc1 (crypto/parisc)
Date: Sun, 12 May 2013 22:49:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1305122248030.5463@ayla.of.borg> (raw)
In-Reply-To: <alpine.DEB.2.00.1305122239040.5463@ayla.of.borg>
On Sun, 12 May 2013, Geert Uytterhoeven wrote:
> However, the full list of errors isn't that unmanageable, so I'm following
> up with a digested list...
lib/mpi/generic_mpih-mul1.c:50:3: error: inconsistent operand constraints in an 'asm': 1 errors in 1 logs
lib/mpi/generic_mpih-mul2.c:49:3: error: inconsistent operand constraints in an 'asm': 1 errors in 1 logs
lib/mpi/generic_mpih-mul3.c:49:3: error: inconsistent operand constraints in an 'asm': 1 errors in 1 logs
lib/mpi/mpih-div.c:142:6: error: inconsistent operand constraints in an 'asm': 1 errors in 1 logs
lib/mpi/mpih-div.c:205:6: error: inconsistent operand constraints in an 'asm': 1 errors in 1 logs
v3.10-rc1/parisc/parisc-allmodconfig
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2013-05-12 20:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 19:30 Build regressions/improvements in v3.10-rc1 Geert Uytterhoeven
2013-05-12 20:41 ` Geert Uytterhoeven
2013-05-12 20:42 ` Build regressions/improvements in v3.10-rc1 (sh) Geert Uytterhoeven
2013-05-12 20:44 ` Build regressions/improvements in v3.10-rc1 (cris) Geert Uytterhoeven
2013-05-14 12:06 ` Geert Uytterhoeven
2013-05-14 16:33 ` Jesper Nilsson
2013-05-12 20:45 ` Build regressions/improvements in v3.10-rc1 (avr) Geert Uytterhoeven
2013-05-13 12:54 ` Hans-Christian Egtvedt
2013-05-13 13:00 ` Geert Uytterhoeven
2013-05-12 20:45 ` Build regressions/improvements in v3.10-rc1 (h8300) Geert Uytterhoeven
2013-05-12 20:46 ` Build regressions/improvements in v3.10-rc1 (mips) Geert Uytterhoeven
2013-06-11 13:37 ` Markos Chandras
2013-05-12 20:47 ` Build regressions/improvements in v3.10-rc1 (powerpc) Geert Uytterhoeven
2013-05-12 20:47 ` Build regressions/improvements in v3.10-rc1 (um) Geert Uytterhoeven
2013-05-12 21:17 ` richard -rw- weinberger
2013-05-13 8:18 ` Geert Uytterhoeven
2013-05-13 9:54 ` Michael Ellerman
2013-05-13 10:02 ` Geert Uytterhoeven
2013-05-13 10:07 ` richard -rw- weinberger
2013-05-13 10:18 ` Geert Uytterhoeven
2013-05-13 10:20 ` richard -rw- weinberger
2013-05-15 2:48 ` Stephen Rothwell
2013-05-13 12:15 ` Michael Ellerman
2013-05-15 2:57 ` Stephen Rothwell
2013-05-15 6:50 ` Geert Uytterhoeven
2013-05-12 20:49 ` Geert Uytterhoeven [this message]
2013-05-12 20:50 ` Build regressions/improvements in v3.10-rc1 (staging) Geert Uytterhoeven
2013-05-12 21:43 ` Greg KH
2013-05-12 20:50 ` Build regressions/improvements in v3.10-rc1 (s390) Geert Uytterhoeven
2013-05-13 7:41 ` Heiko Carstens
2013-05-13 16:41 ` Ben Hutchings
2013-05-12 22:13 ` Build regressions/improvements in v3.10-rc1 Randy Dunlap
2013-05-13 8:37 ` Geert Uytterhoeven
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=alpine.DEB.2.00.1305122248030.5463@ayla.of.borg \
--to=geert@linux-m68k.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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
all inboxes | Powered by JetHome®