public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in•ibm.com>
To: linux-s390@vger•kernel.org
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org,
	Heiko Carstens <heiko.carstens@de•ibm.com>,
	Eric Paris <eparis@redhat•com>
Subject: [-next Nov 17] s390 build break(arch/s390/kernel/compat_wrapper.S)
Date: Tue, 17 Nov 2009 17:36:19 +0530	[thread overview]
Message-ID: <4B0291BB.3090005@in.ibm.com> (raw)
In-Reply-To: <20091117195309.6cc3ead0.sfr@canb.auug.org.au>

Today's next 20091117 build failed on s390 with

arch/s390/kernel/compat_wrapper.S: Assembler messages:
arch/s390/kernel/compat_wrapper.S:1871: Error: operand out of range (164 is not between 0 and 15)
arch/s390/kernel/compat_wrapper.S:1871: Error: junk at end of line: `(%r15)'
make[1]: *** [arch/s390/kernel/compat_wrapper.o] Error 1

The code in question was added by commit 9db3031ac785b068eb4636465eebb7b346c48dbb

fanotify: sys_fanotify_mark declartion

I had applied the following patch to get past another build break reported
against yesterday's next (20091116)

http://marc.info/?l=linux-next&m=125844478708886&w=2 <http://marc.info/?l=linux-next&m=125844478708886&w=2>

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

  reply	other threads:[~2009-11-17 12:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17  8:53 linux-next: Tree for November 17 Stephen Rothwell
2009-11-17 12:06 ` Sachin Sant [this message]
2009-11-17 12:52   ` [-next Nov 17] s390 build break(arch/s390/kernel/compat_wrapper.S) Heiko Carstens
2009-11-17 13:40     ` Eric Paris
2009-11-17 13:55       ` Heiko Carstens
2009-11-17 15:23         ` Eric Paris
2009-11-17 15:50           ` Heiko Carstens
2009-11-17 15:57             ` Eric Paris
2009-11-17 16:14               ` Heiko Carstens
2009-11-18  7:04           ` Heiko Carstens
2009-11-18  9:27             ` Russell King
2009-11-18 14:49             ` Ralf Baechle
2009-11-18 16:02             ` Eric Paris
2009-11-18 16:22               ` Heiko Carstens
2009-11-18 17:34               ` Martin Schwidefsky
2009-11-18 18:41                 ` Heiko Carstens
2009-11-19  8:54                   ` Martin Schwidefsky
2009-11-18 17:24             ` Eric Paris
2009-11-17 17:02 ` linux-next: Tree for November 17 (exofs) Randy Dunlap
2009-11-17 17:08   ` Boaz Harrosh
2009-11-17 17:10     ` Boaz Harrosh
2009-11-17 17:24       ` Boaz Harrosh
2009-11-17 17:48         ` Randy Dunlap
2009-11-17 18:17 ` [PATCH -next] sep: fix 2 warnings Randy Dunlap
2009-11-17 18:29   ` Alan Cox

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=4B0291BB.3090005@in.ibm.com \
    --to=sachinp@in$(echo .)ibm.com \
    --cc=eparis@redhat$(echo .)com \
    --cc=heiko.carstens@de$(echo .)ibm.com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-s390@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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