Jesper Juhl wrote:
On Fri, 25 Mar 2005, Randy.Dunlap wrote:
Jesper Juhl wrote:
Fix spelling in init/Kconfig
Signed-off-by: Jesper Juhl [EMAIL PROTECTED]
--- linux-2.6.12-rc1-mm3-orig/init/Kconfig 2005-03-25 15:29:08.0
+0100
+++ linux-2.6.12-rc1-mm3/init/Kconfig 2005-03-26 02:24
Dave Hansen wrote:
On Fri, 2005-03-25 at 19:00 -0800, Randy.Dunlap wrote:
...
+config DISCONTIGMEM
+ bool Discontigious Memory
+ depends on ARCH_DISCONTIGMEM_ENABLE
+ help
+ If unsure, choose this option over Sparse Memory.
Same question
It's in the third patch
Dave Hansen wrote:
On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote:
I wasn't trying to catch you, but I've already looked at
all 4 patches in the series and I still can't find an
option that is labeled/described as Sparse Memory
The word sparse isn't even in patch 3/4... maybe
Matthew Wilcox wrote:
On Sat, Mar 26, 2005 at 10:50:26PM +, Russell King wrote:
On Sat, Mar 26, 2005 at 09:41:41PM +, Matthew Wilcox wrote:
Any reason you can't merge ARM's options into the drivers/*/Kconfig (with
appropriate conditionals) and use drivers/Kconfig?
Dunno. Haven't gotten
Jesper Juhl wrote:
Fix spelling in init/Kconfig
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
--- linux-2.6.12-rc1-mm3-orig/init/Kconfig 2005-03-25 15:29:08.0
+0100
+++ linux-2.6.12-rc1-mm3/init/Kconfig 2005-03-26 02:24:33.0 +0100
@@ -83,7 +83,7 @@
default y
Dave Hansen wrote:
With sparsemem and memory hotplug there are quite a few options that
we kept adding identically in several different architectures. This
new file allows some of these to be consolidated.
Signed-off-by: Andy Whitcroft <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL
Dave Hansen wrote:
With sparsemem and memory hotplug there are quite a few options that
we kept adding identically in several different architectures. This
new file allows some of these to be consolidated.
Signed-off-by: Andy Whitcroft [EMAIL PROTECTED]
Signed-off-by: Dave Hansen [EMAIL
Jesper Juhl wrote:
Fix spelling in init/Kconfig
Signed-off-by: Jesper Juhl [EMAIL PROTECTED]
--- linux-2.6.12-rc1-mm3-orig/init/Kconfig 2005-03-25 15:29:08.0
+0100
+++ linux-2.6.12-rc1-mm3/init/Kconfig 2005-03-26 02:24:33.0 +0100
@@ -83,7 +83,7 @@
default y
Jeff Garzik wrote:
Andrew Morton wrote:
David McCullough <[EMAIL PROTECTED]> wrote:
Here is a small patch for 2.6.11 that adds a routine:
add_true_randomness(__u32 *buf, int nwords);
It neither applies correctly nor compiles in current kernels. 2.6.11 is
very old in kernel time.
Hrm. This
Christoph Lameter wrote:
We just send an update to Andrew and Jeff that also fixes this issue.
Sadly that patch is >300k so we cannot post it to the list.
you can post it to netdev@oss.sgi.com
it doesn't seem to block large patches.
--
~Randy
-
To unsubscribe from this list: send the line
Jan Engelhardt wrote:
Thanks for confirming. Are you guys interested in this kind of leaks? I have
a list of about a hundred generated by our tool. -yichen
This list is not SUN (where you would have to enter a service contract to
report bugs (efficiently)).
Jan Engelhardt
Just to be clear(er),
Jan Engelhardt wrote:
Thanks for confirming. Are you guys interested in this kind of leaks? I have
a list of about a hundred generated by our tool. -yichen
This list is not SUN (where you would have to enter a service contract to
report bugs (efficiently)).
Jan Engelhardt
Just to be clear(er),
Christoph Lameter wrote:
We just send an update to Andrew and Jeff that also fixes this issue.
Sadly that patch is 300k so we cannot post it to the list.
you can post it to netdev@oss.sgi.com
it doesn't seem to block large patches.
--
~Randy
-
To unsubscribe from this list: send the line
Jeff Garzik wrote:
Andrew Morton wrote:
David McCullough [EMAIL PROTECTED] wrote:
Here is a small patch for 2.6.11 that adds a routine:
add_true_randomness(__u32 *buf, int nwords);
It neither applies correctly nor compiles in current kernels. 2.6.11 is
very old in kernel time.
Hrm. This is
Paul Mackerras wrote:
Just by inspection, this looks like pfn should be changed to
paddr64 >> PAGE_SHIFT in that last line.
Paul.
Agreed, thank you. Patch is attached.
--
~Randy
Fix asm-ppc argument, spotted by Paul Mackerras.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
This is a combination of io_remap_pfn_range patches posted in the
last week or so by Keir Fraser and me.
This description is mostly from Keir's original post.
This patch introduces a new interface function for mapping bus/device
memory: io_remap_pfn_range. This accepts the same parameters as
io_remap_pfn_range():
add io_remap_pfn_range() for all arches;
add MK_IOSPACE_PFN(), GET_IOSPACE(), and GET_PFN()
for all arches but primarily for sparc32/64's extended IO space,
sparc: kill the hack of using low bit of to mean
write_combine or set side-effect (_PAGE_E)
io_remap_pfn_range() remaining callers:
convert all remaining callers of io_remap_page_range()
to io_remap_pfn_range();
add io_remap_page_range() to feature-removal-schedule.txt;
Documentation/feature-removal-schedule.txt |9 +
arch/sh/kernel/cpu/sh4/sq.c|2
io_remap_pfn_range():
convert sparc32/64 callers of io_remap_page_range(with 6 args)
to io_remap_pfn_range(with 5 args);
drivers/char/drm/drm_vm.c |6 +++---
drivers/sbus/char/vfc_dev.c |6 --
drivers/video/fbmem.c |6 +++---
drivers/video/sbuslib.c |8
(from Keir:)
I have audited the drivers/ and sound/ directories. Most uses of
remap_pfn_range are okay, but there are a small handful that are
remapping device memory (mostly AGP and DRM drivers).
Of particular driver is the HPET driver, whose mmap function is broken
even for native (non-Xen)
(from Keir:)
I have audited the drivers/ and sound/ directories. Most uses of
remap_pfn_range are okay, but there are a small handful that are
remapping device memory (mostly AGP and DRM drivers).
Of particular driver is the HPET driver, whose mmap function is broken
even for native (non-Xen)
io_remap_pfn_range():
convert sparc32/64 callers of io_remap_page_range(with 6 args)
to io_remap_pfn_range(with 5 args);
drivers/char/drm/drm_vm.c |6 +++---
drivers/sbus/char/vfc_dev.c |6 --
drivers/video/fbmem.c |6 +++---
drivers/video/sbuslib.c |8
io_remap_pfn_range() remaining callers:
convert all remaining callers of io_remap_page_range()
to io_remap_pfn_range();
add io_remap_page_range() to feature-removal-schedule.txt;
Documentation/feature-removal-schedule.txt |9 +
arch/sh/kernel/cpu/sh4/sq.c|2
io_remap_pfn_range():
add io_remap_pfn_range() for all arches;
add MK_IOSPACE_PFN(), GET_IOSPACE(), and GET_PFN()
for all arches but primarily for sparc32/64's extended IO space,
sparc: kill the hack of using low bit of offset to mean
write_combine or set side-effect
This is a combination of io_remap_pfn_range patches posted in the
last week or so by Keir Fraser and me.
This description is mostly from Keir's original post.
This patch introduces a new interface function for mapping bus/device
memory: io_remap_pfn_range. This accepts the same parameters as
Paul Mackerras wrote:
Just by inspection, this looks like pfn should be changed to
paddr64 PAGE_SHIFT in that last line.
Paul.
Agreed, thank you. Patch is attached.
--
~Randy
Fix asm-ppc argument, spotted by Paul Mackerras.
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
Follow-up to
http://marc.theaimsgroup.com/?l=linux-mm=111049473410099=2
(which has a minor correction, full patch available at:
http://developer.osdl.org/rddunlap/patches/ioremap_pfn_v6.patch)
Built on 9 arches with OSDL PLM.
io_remap_pfn_range() phase 2:
convert all callers of
Keir Fraser wrote:
This patch introduces a new interface function for mapping bus/device
memory: io_remap_pfn_range. This accepts the same parameters as
remap_pfn_range (indeed, by default it is implemented by this existing
function) but should be used in any situation where the caller is not
[EMAIL PROTECTED] wrote:
Hi Greg, PCI folk,
I updated this to change pirq_table_addr to a long, and to add a warning
msg if the PIRQ table wasn't found at the specified address, as per thread
with Matthew Wilcox. Let me know if it's okay. Thanks.
In our hardware situation, the BIOS is unable to
Artem Frolov wrote:
Hello,
I am in the process of testing static defect analyzer on a Linux
kernel source code (see disclosure below).
I found some potential array bounds violations. The pattern is as
follows: bytes are copied from the user space and then buffer is
accessed on index strlen(buf)-1.
Add "kstack=N" boot option for IA-32 (from x86_64).
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
Documentation/kernel-parameters.txt |3 +++
arch/i386/kernel/traps.c|7 +++
2 files changed, 10 insertions(+)
diff -Naurp
Convert "kernel-parameters.txt" to use IA-32 in place of x86
and X86-64 in place of x86_64, to be in line with other
architecture documentation conventions.
Add reference to Documentation/x86_64/boot-options.txt .
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
Keir Fraser wrote:
This patch introduces a new interface function for mapping bus/device
memory: io_remap_pfn_range. This accepts the same parameters as
remap_pfn_range (indeed, by default it is implemented by this existing
function) but should be used in any situation where the caller is not
Keir Fraser wrote:
This patch introduces a new interface function for mapping bus/device
memory: io_remap_pfn_range. This accepts the same parameters as
remap_pfn_range (indeed, by default it is implemented by this existing
function) but should be used in any situation where the caller is not
Convert kernel-parameters.txt to use IA-32 in place of x86
and X86-64 in place of x86_64, to be in line with other
architecture documentation conventions.
Add reference to Documentation/x86_64/boot-options.txt .
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
Add kstack=N boot option for IA-32 (from x86_64).
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
Documentation/kernel-parameters.txt |3 +++
arch/i386/kernel/traps.c|7 +++
2 files changed, 10 insertions(+)
diff -Naurp ./arch/i386/kernel/traps.c~kstack_i386
[EMAIL PROTECTED] wrote:
Hi Greg, PCI folk,
I updated this to change pirq_table_addr to a long, and to add a warning
msg if the PIRQ table wasn't found at the specified address, as per thread
with Matthew Wilcox. Let me know if it's okay. Thanks.
In our hardware situation, the BIOS is unable to
Keir Fraser wrote:
This patch introduces a new interface function for mapping bus/device
memory: io_remap_pfn_range. This accepts the same parameters as
remap_pfn_range (indeed, by default it is implemented by this existing
function) but should be used in any situation where the caller is not
Follow-up to
http://marc.theaimsgroup.com/?l=linux-mmm=111049473410099w=2
(which has a minor correction, full patch available at:
http://developer.osdl.org/rddunlap/patches/ioremap_pfn_v6.patch)
Built on 9 arches with OSDL PLM.
io_remap_pfn_range() phase 2:
convert all callers of
Robert Hancock wrote:
Randy.Dunlap wrote:
The latter one does (before the listed code):
memset(line, 0, LINE_SIZE);
if (len > LINE_SIZE)
len = LINE_SIZE;
if (copy_from_user(line, buf, len - 1))
return -EFAULT;
so isn't line[LINE_SIZE - 1] always 0 ?
In that case,
Robert Hancock wrote:
Artem Frolov wrote:
Hello,
I am in the process of testing static defect analyzer on a Linux
kernel source code (see disclosure below).
I found some potential array bounds violations. The pattern is as
follows: bytes are copied from the user space and then buffer is
accessed
Evgeniy Polyakov wrote:
--- /tmp/empty/crypto_user.h 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/crypto_user.h 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,52 @@
+/*
+ * crypto_user.h
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov <[EMAIL PROTECTED]>
+ *
+ */
+
+#ifndef __CRYPTO_USER_H
Evgeniy Polyakov wrote:
--- /tmp/empty/crypto_main.c 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/crypto_main.c 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,374 @@
+/*
+ * crypto_main.c
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov <[EMAIL PROTECTED]>
+ *
+ */
+struct crypto_session
Laurent CARON wrote:
shafa.hidee wrote:
Hi All,
Where we can find specs for writing driver for Intel PRO 100 card.
Regards
Shafahidee
already supported.
isn't it?
Yes, it is.
You can find a developer's manual for the 8255x NIC at
maximilian attems wrote:
thanks a lot for your review!
you are right much better, added __init to W6692Version().
#Signed-off-by: maximilian attems <[EMAIL PROTECTED]>
Acked-by: Randy Dunlap <[EMAIL PROTECTED]>
diff -pruN -X dontdiff linux-2.6.11-bk8/drivers/isdn/hisax/w6692.c
maximilian attems wrote:
thanks a lot for your review!
you are right much better, added __init to W6692Version().
#Signed-off-by: maximilian attems [EMAIL PROTECTED]
Acked-by: Randy Dunlap [EMAIL PROTECTED]
diff -pruN -X dontdiff linux-2.6.11-bk8/drivers/isdn/hisax/w6692.c
Laurent CARON wrote:
shafa.hidee wrote:
Hi All,
Where we can find specs for writing driver for Intel PRO 100 card.
Regards
Shafahidee
already supported.
isn't it?
Yes, it is.
You can find a developer's manual for the 8255x NIC at
Evgeniy Polyakov wrote:
--- /tmp/empty/crypto_main.c 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/crypto_main.c 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,374 @@
+/*
+ * crypto_main.c
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov [EMAIL PROTECTED]
+ *
+ */
+struct crypto_session
Evgeniy Polyakov wrote:
--- /tmp/empty/crypto_user.h 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/crypto_user.h 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,52 @@
+/*
+ * crypto_user.h
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov [EMAIL PROTECTED]
+ *
+ */
+
+#ifndef __CRYPTO_USER_H
Robert Hancock wrote:
Artem Frolov wrote:
Hello,
I am in the process of testing static defect analyzer on a Linux
kernel source code (see disclosure below).
I found some potential array bounds violations. The pattern is as
follows: bytes are copied from the user space and then buffer is
accessed
Robert Hancock wrote:
Randy.Dunlap wrote:
The latter one does (before the listed code):
memset(line, 0, LINE_SIZE);
if (len LINE_SIZE)
len = LINE_SIZE;
if (copy_from_user(line, buf, len - 1))
return -EFAULT;
so isn't line[LINE_SIZE - 1] always 0 ?
In that case, yes (I
(resend)
Use NULL instead of 0 for pointer (sparse warning):
fs/reiserfs/namei.c:611:50: warning: Using plain integer as NULL pointer
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
fs/reiserfs/namei.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Naurp
Ben Dooks wrote:
On Mon, Mar 14, 2005 at 04:07:01PM -0800, Randy.Dunlap wrote:
(resend)
Fix (22) bitfield/boolean sparse warnings:
include/linux/mtd/flashchip.h:65:23: warning: dubious one-bit signed bitfield
include/linux/mtd/flashchip.h:66:23: warning: dubious one-bit signed bitfield
caught
Ben Dooks wrote:
On Mon, Mar 14, 2005 at 04:03:29PM -0800, Randy.Dunlap wrote:
(resend)
Use C99 struct inits as requested by sparse:
fs/proc/base.c:738:2: warning: obsolete struct initializer, use C99 syntax
fs/proc/base.c:739:2: warning: obsolete struct initializer, use C99 syntax
I posted
(resend)
Put function prototypes for memset() and memcpy() ahead of where
there are used, to kill sparse warnings:
arch/x86_64/boot/compressed/../../../../lib/inflate.c:317:3: warning: undefined
identifier 'memset'
arch/x86_64/boot/compressed/../../../../lib/inflate.c:601:11: warning:
(resend)
Fix (22) bitfield/boolean sparse warnings:
include/linux/mtd/flashchip.h:65:23: warning: dubious one-bit signed bitfield
include/linux/mtd/flashchip.h:66:23: warning: dubious one-bit signed bitfield
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
(resend)
Use C99 struct inits as requested by sparse:
fs/proc/base.c:738:2: warning: obsolete struct initializer, use C99 syntax
fs/proc/base.c:739:2: warning: obsolete struct initializer, use C99 syntax
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
fs/proc/base.c |4 ++--
1
Andrew Morton wrote:
"Randy.Dunlap" <[EMAIL PROTECTED]> wrote:
Nope. Please use %Z for size_t args.
Yeps. Here it is.
--
~Randy
Fix gcc printk arg type warnings:
drivers/char/tpm/tpm.c:145: warning: unsigned int format, different type arg (arg 5)
drivers/char/tpm/tpm.c:1
(Kylene, please add TPM info to MAINTAINERS or CREDITS)
Fix gcc printk arg type warnings:
drivers/char/tpm/tpm.c:145: warning: unsigned int format, different type arg
(arg 5)
drivers/char/tpm/tpm.c:153: warning: int format, different type arg (arg 4)
drivers/char/tpm/tpm.c:190: warning: int
maximilian attems wrote:
Fix hfc_sx section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/hfc_sx.o .text refers to 204d R_386_32
.init.data
Error: ./drivers/isdn/hisax/hfc_sx.o .text refers to 205c R_386_32
.init.data
Error: ./drivers/isdn/hisax/hfc_sx.o
maximilian attems wrote:
Fix elsa section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/elsa.o .text refers to 3d28 R_386_32
.init.data
Error: ./drivers/isdn/hisax/elsa.o .text refers to 3d37 R_386_32
.init.data
Error: ./drivers/isdn/hisax/elsa.o .text
maximilian attems wrote:
Fix sedlbauer section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/sedlbauer.o .text refers to 235f R_386_32
.init.data
Error: ./drivers/isdn/hisax/sedlbauer.o .text refers to 236e R_386_32
.init.data
Error:
maximilian attems wrote:
Fix w6692 section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/w6692.o .text refers to 002f R_386_32
.init.data
Signed-off-by: maximilian attems <[EMAIL PROTECTED]>
diff -pruN -X dontdiff linux-2.6.11-bk8/drivers/isdn/hisax/w6692.c
maximilian attems wrote:
Fix teles3 section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/teles3.o .text refers to 11ab R_386_32
.init.data
Error: ./drivers/isdn/hisax/teles3.o .text refers to 11ba R_386_32
.init.data
Error: ./drivers/isdn/hisax/teles3.o
Sam Ravnborg wrote:
On Mon, Mar 14, 2005 at 01:38:11PM -0800, Randy.Dunlap wrote:
Indeed, it's actually much worse with that patch section added. :(
I don't know how I got there.
Sam, can you drop the very first patch section here, or shall I send
a new patch for this?
Incremental patch please
Keith Owens wrote:
On Mon, 14 Mar 2005 11:02:09 -0800,
"Randy.Dunlap" <[EMAIL PROTECTED]> wrote:
Reduce noise in 'make buildcheck' that is caused by CONFIG_DEBUG_INFO=y.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
scripts/reference_discarded.pl |3 +++
scr
Miquel van Smoorenburg wrote:
In article <[EMAIL PROTECTED]>,
Berkley Shands <[EMAIL PROTECTED]> wrote:
I have not found any documentation of efforts to overcome the 2TB
partition limit,
config LBD
bool "Support for Large Block Devices"
depends on X86 || MIPS32 || PPC32 ||
Reduce noise in 'make buildcheck' that is caused by CONFIG_DEBUG_INFO=y.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
diffstat:=
scripts/reference_discarded.pl |3 +++
scripts/reference_init.pl |1 +
2 files changed, 4 insertions(+)
diff -Naurp
Nguyen, Tom L wrote:
Monday, March 14, 2005 3:01 AM David Vrabel wrote:
This patch includes PCIEAER-HOWTO.txt, which describes how the PCI
Express Advanced Error Reporting Root driver works.
--- linux-2.6.11-rc5/Documentation/PCIEAER-HOWTO.txt
Could this be placed in a sub-system subdirectory
Nguyen, Tom L wrote:
Monday, March 14, 2005 3:01 AM David Vrabel wrote:
This patch includes PCIEAER-HOWTO.txt, which describes how the PCI
Express Advanced Error Reporting Root driver works.
--- linux-2.6.11-rc5/Documentation/PCIEAER-HOWTO.txt
Could this be placed in a sub-system subdirectory
Reduce noise in 'make buildcheck' that is caused by CONFIG_DEBUG_INFO=y.
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
scripts/reference_discarded.pl |3 +++
scripts/reference_init.pl |1 +
2 files changed, 4 insertions(+)
diff -Naurp
Miquel van Smoorenburg wrote:
In article [EMAIL PROTECTED],
Berkley Shands [EMAIL PROTECTED] wrote:
I have not found any documentation of efforts to overcome the 2TB
partition limit,
config LBD
bool Support for Large Block Devices
depends on X86 || MIPS32 || PPC32 || ARCH_S390_31
Keith Owens wrote:
On Mon, 14 Mar 2005 11:02:09 -0800,
Randy.Dunlap [EMAIL PROTECTED] wrote:
Reduce noise in 'make buildcheck' that is caused by CONFIG_DEBUG_INFO=y.
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
scripts/reference_discarded.pl |3 +++
scripts/reference_init.pl
Sam Ravnborg wrote:
On Mon, Mar 14, 2005 at 01:38:11PM -0800, Randy.Dunlap wrote:
Indeed, it's actually much worse with that patch section added. :(
I don't know how I got there.
Sam, can you drop the very first patch section here, or shall I send
a new patch for this?
Incremental patch please
maximilian attems wrote:
Fix teles3 section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/teles3.o .text refers to 11ab R_386_32
.init.data
Error: ./drivers/isdn/hisax/teles3.o .text refers to 11ba R_386_32
.init.data
Error: ./drivers/isdn/hisax/teles3.o
maximilian attems wrote:
Fix w6692 section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/w6692.o .text refers to 002f R_386_32
.init.data
Signed-off-by: maximilian attems [EMAIL PROTECTED]
diff -pruN -X dontdiff linux-2.6.11-bk8/drivers/isdn/hisax/w6692.c
maximilian attems wrote:
Fix sedlbauer section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/sedlbauer.o .text refers to 235f R_386_32
.init.data
Error: ./drivers/isdn/hisax/sedlbauer.o .text refers to 236e R_386_32
.init.data
Error:
maximilian attems wrote:
Fix elsa section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/elsa.o .text refers to 3d28 R_386_32
.init.data
Error: ./drivers/isdn/hisax/elsa.o .text refers to 3d37 R_386_32
.init.data
Error: ./drivers/isdn/hisax/elsa.o .text
maximilian attems wrote:
Fix hfc_sx section references:
convert __initdata to __devinitdata.
Error: ./drivers/isdn/hisax/hfc_sx.o .text refers to 204d R_386_32
.init.data
Error: ./drivers/isdn/hisax/hfc_sx.o .text refers to 205c R_386_32
.init.data
Error: ./drivers/isdn/hisax/hfc_sx.o
(Kylene, please add TPM info to MAINTAINERS or CREDITS)
Fix gcc printk arg type warnings:
drivers/char/tpm/tpm.c:145: warning: unsigned int format, different type arg
(arg 5)
drivers/char/tpm/tpm.c:153: warning: int format, different type arg (arg 4)
drivers/char/tpm/tpm.c:190: warning: int
Andrew Morton wrote:
Randy.Dunlap [EMAIL PROTECTED] wrote:
Nope. Please use %Z for size_t args.
Yeps. Here it is.
--
~Randy
Fix gcc printk arg type warnings:
drivers/char/tpm/tpm.c:145: warning: unsigned int format, different type arg (arg 5)
drivers/char/tpm/tpm.c:153: warning: int format
(resend)
Use C99 struct inits as requested by sparse:
fs/proc/base.c:738:2: warning: obsolete struct initializer, use C99 syntax
fs/proc/base.c:739:2: warning: obsolete struct initializer, use C99 syntax
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
fs/proc/base.c |4 ++--
1
(resend)
Fix (22) bitfield/boolean sparse warnings:
include/linux/mtd/flashchip.h:65:23: warning: dubious one-bit signed bitfield
include/linux/mtd/flashchip.h:66:23: warning: dubious one-bit signed bitfield
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
include/linux/mtd/flashchip.h
(resend)
Put function prototypes for memset() and memcpy() ahead of where
there are used, to kill sparse warnings:
arch/x86_64/boot/compressed/../../../../lib/inflate.c:317:3: warning: undefined
identifier 'memset'
arch/x86_64/boot/compressed/../../../../lib/inflate.c:601:11: warning:
Ben Dooks wrote:
On Mon, Mar 14, 2005 at 04:03:29PM -0800, Randy.Dunlap wrote:
(resend)
Use C99 struct inits as requested by sparse:
fs/proc/base.c:738:2: warning: obsolete struct initializer, use C99 syntax
fs/proc/base.c:739:2: warning: obsolete struct initializer, use C99 syntax
I posted
Ben Dooks wrote:
On Mon, Mar 14, 2005 at 04:07:01PM -0800, Randy.Dunlap wrote:
(resend)
Fix (22) bitfield/boolean sparse warnings:
include/linux/mtd/flashchip.h:65:23: warning: dubious one-bit signed bitfield
include/linux/mtd/flashchip.h:66:23: warning: dubious one-bit signed bitfield
caught
(resend)
Use NULL instead of 0 for pointer (sparse warning):
fs/reiserfs/namei.c:611:50: warning: Using plain integer as NULL pointer
Signed-off-by: Randy Dunlap [EMAIL PROTECTED]
diffstat:=
fs/reiserfs/namei.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Naurp
Reg Clemens wrote:
Any way to get larger fonts with xconfig?
On my system they are just about microscopic.
I can do a to go to a different screen resolution,
but then I have all sorts of scanning to deal with.
Ive looked for documentation, but didnt find it in any of the
places I looked...
No
Peter Chubb wrote:
Microstate accounting: Add the I386 system call.
arch/i386/kernel/entry.S |2 +-
include/asm-i386/unistd.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6-ustate/arch/i386/kernel/entry.S
Peter Chubb wrote:
Microstate accounting: Add the I386 system call.
arch/i386/kernel/entry.S |2 +-
include/asm-i386/unistd.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6-ustate/arch/i386/kernel/entry.S
Reg Clemens wrote:
Any way to get larger fonts with xconfig?
On my system they are just about microscopic.
I can do a ctlalt?+ to go to a different screen resolution,
but then I have all sorts of scanning to deal with.
Ive looked for documentation, but didnt find it in any of the
places I
maximilian attems wrote:
Fix cyrix section references:
convert __initdata to __devinitdata.
Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .text refers to 0379
R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .text refers to 0399
R_386_32 .init.data
Error:
maximilian attems wrote:
Fix cyrix section references:
convert __initdata to __devinitdata.
Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .text refers to 0379
R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .text refers to 0399
R_386_32 .init.data
Error:
Evgeniy Polyakov wrote:
--- /tmp/empty/crypto_lb.c 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/crypto_lb.c 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,634 @@
+/*
+ * crypto_lb.c
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov <[EMAIL PROTECTED]>
+ */
+
+
+static
Evgeniy Polyakov wrote:
--- /tmp/empty/crypto_lb.c 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/crypto_lb.c 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,634 @@
+/*
+ * crypto_lb.c
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov [EMAIL PROTECTED]
+ */
+
+
+static
DHollenbeck wrote:
I had hoped that the proper discipline in rejecting non-critical patches
would have pertained. I remain unconvinced that the .y releases are
anything but noise that should have been kept elsewhere. After reading
through a patch summary, I see this as typical:
Matt Mackall wrote:
On Wed, Mar 09, 2005 at 12:39:23AM -0800, Greg KH wrote:
And to further test this whole -stable system, I've released 2.6.11.2.
It contains one patch, which is already in the -bk tree, and came from
the security team (hence the lack of the longer review cycle).
It's available
Matt Mackall wrote:
On Wed, Mar 09, 2005 at 12:39:23AM -0800, Greg KH wrote:
And to further test this whole -stable system, I've released 2.6.11.2.
It contains one patch, which is already in the -bk tree, and came from
the security team (hence the lack of the longer review cycle).
It's available
DHollenbeck wrote:
I had hoped that the proper discipline in rejecting non-critical patches
would have pertained. I remain unconvinced that the .y releases are
anything but noise that should have been kept elsewhere. After reading
through a patch summary, I see this as typical:
Evgeniy Polyakov wrote:
--- /tmp/empty/acrypto.h 1970-01-01 03:00:00.0 +0300
+++ ./acrypto/acrypto.h 2005-03-07 20:35:36.0 +0300
@@ -0,0 +1,245 @@
+/*
+ * acrypto.h
+ *
+ * Copyright (c) 2004 Evgeniy Polyakov <[EMAIL PROTECTED]>
+ *
+ */
+
+#ifdef __KERNEL__
+
+#define
201 - 300 of 525 matches
Mail list logo
