Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Some instances of the "bool" statement have what appear to be
dependencies like "dep_bool" after the 2nd argument, which are
silently ignored by all current parsers. I have either trimmed
the arguments or converted the "bool" to "dep_bool" as seemed
appropriate.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Five symbols CONFIG_ACER_PICA_61, CONFIG_MIPS_EV96100, CONFIG_MIPS_EV64120,
CONFIG_MIPS_ATLAS, and CONFIG_MIPS_MALTA depend on CONFIG_EXPERIMENTAL but
do not say so in their banners.
Tom Rini [Mon, 15 Jul 2002 05:59:21 +0000 (22:59 -0700)]
[PATCH] Don't always ask about Intel RNGs
Hello. The following patch hides the option for Intel (i8x0) RNG
support when it's not a useful option. This is based off of a patch
That was accepted in 2.4.19-pre6. While I suspect this is an ia32-only
option, it is possible that it's used on ia64 as well, so we test for
both before offering Intel i8x0 RNG support.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Andreas Dilger [Mon, 15 Jul 2002 05:54:15 +0000 (22:54 -0700)]
[PATCH] 2.5 i_size_high fixup
this patch is a minor fixup to ext2/inode.c to avoid displaying the
high 32 bits of the size for anything other than regular files. For
sockets, pipes, symlinks, etc it doesn't make sense to have a value
larger than 2GB, and this has already been fixed in ext3 and e2fsprogs.
Documentation/DocBook/kernel-api.tmpl includes code that has no
documentation on 2.5.24, the empty sections mess up the sgml. Comment
out these sections until sombody adds docs to the code.
Robert Kuebel [Mon, 15 Jul 2002 05:52:41 +0000 (22:52 -0700)]
[PATCH] namespace.c - compiler warning
init_rootfs() (from ramfs) doesn't appear in any header file. I didn't
see any that looked like a good home, so lets put a prototype at the top
of fs/namespace.c. This only use of this function is in namespace.c.
The arch-determining symbol CONFIG_SH in drivers/mtd/maps/Config.in
should be CONFIG_SUPERH.
[Rusty: this is a resend of 'PATCH 2.5: kconfig wrong arch symbol';
it should apply now that my earlier patch which trod on the context
has been merged into 2.5.24]
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
for this purpose.
Divorces task xid<->request slot mapping from the internals of the
rpc_waitqueue xprt->pending. Instead xprt_lookup_rqst() is made to
search a dedicated list (xprt->recv) on which the request slot is
placed immediately after being allocated to a task. The new queue is
protected using the spinlock xprt->sock_lock rather than the generic
RPC task lock.
Both udp_data_ready() and tcp_data_ready() (well tcp_read_request()
actually) now need to protect against the request being removed from
the xprt->recv list while they copy the RPC reply data from the skb.
On the other hand, they no longer need to worry about the task
disappearing from xprt->pending. This means that rpc_lock_task() hack
can be replaced by the spinlock xprt->sock_lock.
Fixes an obvious bug in __nfs_refresh_inode(): after updating the
attribute cache, if we discover that the data cache is invalid don't
call nfs_zap_caches() as that will also reinvalidate the attribute
cache.
This bug plays havoc with the new lookup/revalidation code in 2.4.19
since it forces a lot of unnecessary extra GETATTR RPC calls.
Douglas Gilbert [Sun, 14 Jul 2002 12:27:21 +0000 (05:27 -0700)]
[PATCH] sg driver against lk 2.5.25
This patch is against lk 2.5.25 . It
- fixes copy_from/to_user() [William Stinson from dj tree]
- disables kiobuf use, so it will compile without kiobufs
The latter change is so Andrew Morton can remove kiobufs
as suggested in his "direct-to-BIO for O_DIRECT" thread.
SuSv3 says: "The mprotect() function shall fail if:
[EACCES]
The prot argument specifies a protection that violates the access
permission the process has to the underlying memory object.
[EAGAIN]
The prot argument specifies PROT_WRITE over a MAP_PRIVATE mapping and
there are insufficient memory resources to reserve for locking the
private page.
[EINVAL]
The addr argument is not a multiple of the page size as returned by
sysconf().
[ENOMEM]
Addresses in the range [addr,addr+len) are invalid for the address
space of a process, or specify one or more pages which are not mapped.
[ENOMEM]
The prot argument specifies PROT_WRITE on a MAP_PRIVATE mapping, and
it would require more space than the system is able to supply for
locking the private pages, if required.
[ENOTSUP]
The implementation does not support the combination of accesses
requested in the prot argument."
This fixes error code of mprotect() of the ENOMEM case.
[EBUSY]
Some or all of the addresses in the range starting at addr and
continuing for len bytes are locked, and MS_INVALIDATE is
specified.
[EINVAL]
The value of flags is invalid.
[EINVAL]
The value of addr is not a multiple of the page size {PAGESIZE}.
[ENOMEM]
The addresses in the range starting at addr and continuing for len
bytes are outside the range allowed for the address space of a process
or specify one or more pages that are not mapped."
This fixes error code of msync() of the EINVAL case.
Anton Blanchard [Sun, 14 Jul 2002 11:08:49 +0000 (04:08 -0700)]
[PATCH] Allow non zero boot cpu
A partitioned ppc64 machine can have a boot cpuid anywhere from 0 to 31.
With the non linear cpu changes in 2.5.24 we must set up the initial task
to start on the boot cpu. (since it isnt always 0 now)
With this patch I am able to boot on cpus other than 0. I also tested
discontiguous cpuids. So the non linear cpu stuff checks out OK.
I'd like Florent credited -- he is maintaining 2.4.X version and
helping with development. Kill warnings by rearranging code / adding
prototypes. Enable using separate console (so user sees progress and X
suspend/resume works properly), forward-port of updates from Florent
and stop using own PRINTK stuff (mostly). Reading now primarily uses
block_device(), this should enable more cleanups. Fixed double free on
error path.