linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] i386: let REGPARM no longer depend on EXPERIMENTAL
Date: Sun, 8 Jan 2006 16:22:30 +0100	[thread overview]
Message-ID: <20060108152230.GL3774@stusta.de> (raw)

REGPARM has already gotten much testing, what about removing the 
dependency on EXPERIMENTAL?

Additionally, this patch does:
- remove the useless "default n"
- remove note regarding binary only modules (nowadays, there are even
  some binary only modules compiled with REGPARM=y available)


Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

This patch was already sent on:
- 6 Jan 2006

--- linux-2.6.15-mm1-full/arch/i386/Kconfig.old	2006-01-05 23:28:27.000000000 +0100
+++ linux-2.6.15-mm1-full/arch/i386/Kconfig	2006-01-05 23:28:42.000000000 +0100
@@ -626,13 +626,10 @@
 	default y
 
 config REGPARM
-	bool "Use register arguments (EXPERIMENTAL)"
-	depends on EXPERIMENTAL
-	default n
+	bool "Use register arguments"
 	help
 	Compile the kernel with -mregparm=3. This uses a different ABI
 	and passes the first three arguments of a function call in registers.
-	This will probably break binary only modules.
 
 config SECCOMP
 	bool "Enable seccomp to safely compute untrusted bytecode"


             reply	other threads:[~2006-01-08 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 15:22 Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-06  2:25 [2.6 patch] i386: let REGPARM no longer depend on EXPERIMENTAL Adrian Bunk
2006-01-06  7:52 ` Jan Engelhardt

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=20060108152230.GL3774@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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 NNTP newsgroup(s).