linux.git/arch/cris, branch v2.6.14

[NETFILTER]: Fix OOPSes on machines with discontiguous cpu numbering.

2005-10-13T21:41:23+00:00

Original patch by Harald Welte, with feedback from Herbert Xu
and testing by S�bastien Bernard.

EBTABLES, ARP tables, and IP/IP6 tables all assume that cpus
are numbered linearly.  That is not necessarily true.

This patch fixes that up by calculating the largest possible
cpu number, and allocating enough per-cpu structure space given
that.

Signed-off-by: David S. Miller

[PATCH] gfp flags annotations - part 1

2005-10-08T22:00:57+00:00

 - added typedef unsigned int __nocast gfp_t;

 - replaced __nocast uses for gfp flags with gfp_t - it gives exactly
   the same warnings as far as sparse is concerned, doesn't change
   generated code (from gcc point of view we replaced unsigned int with
   typedef) and documents what's going on far better.

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

kbuild: rename prepare to archprepare to fix dependency chain

2005-09-11T20:30:22+00:00

When introducing the generic asm-offsets.h support the dependency
chain for the prepare targets was changed. All build scripts expecting
include/asm/asm-offsets.h to be made when using the prepare target would broke.
With the limited number of prepare targets left in arch Makefiles
the trivial solution was to introduce a new arch specific target: archprepare

The dependency chain looks like this now:

prepare
  |
  +--> prepare0
         |
         +--> archprepare
                |
		+--> scripts_basic
                +--> prepare1
                       |
                       +---> prepare2
                               |
                               +--> prepare3

So prepare 3 is processed before prepare2 etc.
This guaantees that the asm symlink, version.h, scripts_basic
are all updated before archprepare is processed.

prepare0 which build the asm-offsets.h file will need the
actions performed by archprepare.

The head target is now named prepare, because users scripts will most
likely use that target, but prepare-all has been kept for compatibility.
Updated Documentation/kbuild/makefiles.txt.

Signed-off-by: Sam Ravnborg

kbuild: cris use generic asm-offsets.h support

2005-09-09T20:44:31+00:00

Cris has a dedicated asm-offsets.c file per subarchitecture.
So a symlink is created to put the desired asm-offsets.c file
in $(ARCH)/kernel
This is absolutely not good practice, but it was the trick
used in the rest of the cris code.

Signed-off-by: Sam Ravnborg

[PATCH] NTP: ntp-helper functions

2005-09-07T23:57:34+00:00

This patch cleans up a commonly repeated set of changes to the NTP state
variables by adding two helper inline functions:

ntp_clear(): Clears the ntp state variables

ntp_synced(): Returns 1 if the system is synced with a time server.

This was compile tested for alpha, arm, i386, x86-64, ppc64, s390, sparc,
sparc64.

Signed-off-by: John Stultz 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] arch/cris/Kconfig.debug: use lib/Kconfig.debug

2005-09-05T07:06:19+00:00

This patch converts arch/cris/Kconfig.debug to using lib/Kconfig.debug.

This should fix a compile error in 2.6.13-rc4 caused by a missing
CONFIG_LOG_BUF_SHIFT definition.

While I was editing this file, I also converted some spaces to tabs.

Signed-off-by: Adrian Bunk 
Acked-by: Mikael Starvik 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] convert signal handling of NODEFER to act like other Unix boxes.

2005-08-29T17:03:11+00:00

It has been reported that the way Linux handles NODEFER for signals is
not consistent with the way other Unix boxes handle it.  I've written a
program to test the behavior of how this flag affects signals and had
several reports from people who ran this on various Unix boxes,
confirming that Linux seems to be unique on the way this is handled.

The way NODEFER affects signals on other Unix boxes is as follows:

1) If NODEFER is set, other signals in sa_mask are still blocked.

2) If NODEFER is set and the signal is in sa_mask, then the signal is
still blocked. (Note: this is the behavior of all tested but Linux _and_
NetBSD 2.0 *).

The way NODEFER affects signals on Linux:

1) If NODEFER is set, other signals are _not_ blocked regardless of
sa_mask (Even NetBSD doesn't do this).

2) If NODEFER is set and the signal is in sa_mask, then the signal being
handled is not blocked.

The patch converts signal handling in all current Linux architectures to
the way most Unix boxes work.

Unix boxes that were tested:  DU4, AIX 5.2, Irix 6.5, NetBSD 2.0, SFU
3.5 on WinXP, AIX 5.3, Mac OSX, and of course Linux 2.6.13-rcX.

* NetBSD was the only other Unix to behave like Linux on point #2. The
main concern was brought up by point #1 which even NetBSD isn't like
Linux.  So with this patch, we leave NetBSD as the lonely one that
behaves differently here with #2.

Signed-off-by: Linus Torvalds

It wasn't just x86-64 that had hardcoded VM_FAULT_xxx numbers

2005-08-04T15:33:38+00:00

Fix up arm26, cris, frv, m68k, parisc and sh64 too..

[PATCH] CRIS update: new subarchitecture v32

2005-07-27T23:26:01+00:00

New CRIS sub architecture named v32.

From: Dave Jones 

	Fix swapped kmalloc args

Signed-off-by: Mikael Starvik 
Signed-off-by: Dave Jones 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] CRIS update: updates for 2.6.12

2005-07-27T23:26:01+00:00

Patches to make CRIS work with 2.6.12.

Signed-off-by: Mikael Starvik 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds