--On Monday, March 14, 2005 20:49:30 +0100 Sam Ravnborg <[EMAIL PROTECTED]>
wrote:
> On Mon, Mar 14, 2005 at 11:39:37AM -0800, Dave Hansen wrote:
>> I'm having some intermittent build problems on 2.6.11-bk10. First of
>> all, doing a 'make -j8 O=... install' errors out not being able to find
>>
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 |
On Mar 14, 2005 21:09 +0100, Sam Ravnborg wrote:
> I already applied your original patch (end of January) but only this week
> it hit Linus' tree.
> I think ctags users will just upgrade if their ctgs does not support
> --extra=+f.
I have ctags-5.4.2 (24 Jan 2003) and it has the --extra=+f suppor
Hello.
Brian Gerst wrote:
Can you tell me how the invisible high-word (invisible in VM-86, and
in real mode) could possibly harm something running in VM-86 or
read-mode ??? I don't even think it's a BUG. If the transition
into and out of VM-86 doesn't handle the fact that the high-word
of the stac
On Wed, Feb 09, 2005 at 10:40:11AM -0800, Matt Mackall wrote:
> Add PREEMPT to UTS_VERSION where enabled as is done for SMP to make
> preempt kernels easily identifiable.
I have the following patch in my tree now. It has the advantage that
compile.h gets updated when you change the PREEMPT setting.
Rewrite initialiser for proc_oom_adjust_operations,
and add __user annotations to oom_adjust_{read|write}
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
diff -urN -X ../dontdiff linux-2.6.11-bk10/fs/proc/base.c
linux-2.6.11-bk10-procfs/fs/proc/base.c
--- linux-2.6.11-bk10/fs/proc/base.c2005-03
On Mon, Mar 14, 2005 at 09:49:17PM +0100, Sam Ravnborg wrote:
> On Wed, Feb 09, 2005 at 10:40:11AM -0800, Matt Mackall wrote:
> > Add PREEMPT to UTS_VERSION where enabled as is done for SMP to make
> > preempt kernels easily identifiable.
> I have the following patch in my tree now. It has the adva
discontig.c has some assumptions that mem_map[]s inside of a node are
contiguous. Teach it to make sure that each region that it's brining
online is actually made up of valid ranges of ram.
Written-by: Andy Whitcroft <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
memhot
The following four patches provide the last needed changes before the
introduction of sparsemem. For a more complete description of what this
will do, please see this patch:
http://www.sr71.net/patches/2.6.11/2.6.11-bk7-mhp1/broken-out/B-sparse-150-sparsemem.patch
or previous posts on the subjec
We _know_ which node pages in general belong to, at least at a
very gross level in node_{start,end}_pfn[]. Use those to target
the allocations of pages.
Signed-off-by: Andy Whitcroft <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
arch/ia64/mm/numa.c
Introduce a simple allocator for the NUMA remap space. This space is
very scarce, used for structures which are best allocated node local.
This mechanism is also used on non-NUMA ia64 systems with a vmem_map
to keep the pgdat->node_mem_map initialized in a consistent place for
all architectures.
Generify the value fields in the page_flags. The aim is to allow
the location and size of these fields to be varied. Additionally we
want to move away from fixed allocations per field whilst still
enforcing the overall bit utilisation limits. We rely on the
compiler to spot and optimise the acc
>
> > On popular request 'make install' no longer try to update vmlinux.
> > This is to avoid errornous recompilation when installing the kernel
> > as root especially when fetching kernel via nfs where path may have
> > changed.
>
> That's frigging annoying. It's worked that way for ages, and a
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 || SUPERH
help
Domen Puncer wrote:
On 14/03/05 12:35 -0500, Wen Xiong wrote:
Domen Puncer wrote:
Just some nitpicking...
Hi Domen, all,
Thanks for your comments. I did some minor changes for patch1 based on
Domen's comment.
And i missed, what is probably a bug:
+module_param(jsm_debug,
Move bulk of e1000_watchdog to a workqueue to make it safe to call
functions which can sleep.
Signed-off-by: John W. Linville <[EMAIL PROTECTED]>
---
The e1000 driver uses a timer to invoke e1000_watchdog().
e1000_watchdog() calls e1000_check_for_link() which can call
e1000_config_dsp_after_link_c
>> > On popular request 'make install' no longer try to update vmlinux.
>> > This is to avoid errornous recompilation when installing the kernel
>> > as root especially when fetching kernel via nfs where path may have
>> > changed.
>>
>> That's frigging annoying. It's worked that way for ages, and
On Thu, 2005-03-10 at 17:47, Andrew Morton wrote:
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> >
> > So, why is these slab cache are not getting purged/shrinked even
> > under memory pressure ? (I have seen lowmem as low as 6MB). What
> > can I do to keep the machine healthy ?
>
> Tried incre
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_S3
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
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. I already ha
On Sat, Feb 26, 2005 at 09:50:02PM +1100, Keith Owens wrote:
> Make it easier to generate maps for debugging kallsyms problems.
> debug_kallsyms is only a debugging target so no help or silent mode.
>
> Signed-off-by: Keith Owens
Applied to my kbuild tree.
I will remove it when we stop see kallsy
On Mon, Mar 14, 2005 at 10:14:17AM +0100, Vegard Lima wrote:
> Hello,
>
> in the long thread on "[request for inclusion] Realtime LSM" there
> doesn't appear to be too many people who has actually tested the
> nice-and-rt-prio-rlimits.patch. Well, it works for me...
>
> However, the patch to pam_
On Mon, 2005-03-14 at 16:19 +0100, Segher Boessenkool wrote:
> > On possibiliy would be to have the kernel replace spaces with
> > underscores for the sake of matching. That would make life easier for
> > everybody.
>
> Yes, that'll probably work just fine. Or use 0xb1, showing that this
> is "p
On Mon, 14 Mar 2005 13:14:43 -0800
Dave Hansen <[EMAIL PROTECTED]> wrote:
> Three of these are i386-only, but one of them reorganizes the macros
> used to manage the space in page->flags, and will affect all platforms.
> There are analogous patches to the i386 ones for ppc64, ia64, and
> x86_64, b
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. I
On Mon, 14 Mar 2005 22:43:41 +0100,
Sam Ravnborg <[EMAIL PROTECTED]> wrote:
>On Sat, Feb 26, 2005 at 09:50:02PM +1100, Keith Owens wrote:
>> Make it easier to generate maps for debugging kallsyms problems.
>> debug_kallsyms is only a debugging target so no help or silent mode.
>>
>> Signed-off-by
Hi Arjan,
You wrote:
> shouldn't we just fix the alignment code instead that the overflow case
> doesn't align to 0???
> that sounds really odd.
How? You have to align and you are out of bits for representing the
next number. What is the next number you can round to? "null" right!
Just remember
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm3/
Hi Andrew,
DRM/i915 does not work on my Dell Dimension 3000 (i865 chipset).
It's the first -mm kernel I try on this box. I don't whether previous -mm
worked or not.
Anyway, 2.6.11 works great.
On Mon, 14 Mar 2005 21:13:36 +1100
Paul Mackerras <[EMAIL PROTECTED]> wrote:
> Jake Moilanen writes:
>
> > diff -puN fs/binfmt_elf.c~nx-user-ppc64 fs/binfmt_elf.c
> > --- linux-2.6-bk/fs/binfmt_elf.c~nx-user-ppc64 2005-03-08 16:08:54
> > -06:00
> > +++ linux-2.6-bk-moilanen/fs/binfmt_elf.c
Russell King wrote:
> The only thing I'd question is whether we really need to BUG_ON() here.
> ISTR Linus' policy for BUG()/BUG_ON() was only if the condition lead
> directly to a filesystem-corrupting bug.
I consider it quite effective to flag interface violations.
Programming by contract anyone
> We already have the 'quiet' option, but even so, I think the kernel is *way*
> too verbose. Someone needs to make a personal crusade out of removing
> unneeded and unjustified printks from the kernel before it really gets better
> though...
Oh well, I admit going backward here with my new r
Is the qla2xxx dirver not capable of fail over support? under
Documentation/* for the qla2xxx release notes, it says in a earlier
revision that fail over was made optional. Was the optional support
removed? If it is capable of fail over, what are the means of
enable/accessing the ability?
Thank
On Tue, 15 Mar 2005, Benjamin Herrenschmidt wrote:
We already have the 'quiet' option, but even so, I think the kernel is *way*
too verbose. Someone needs to make a personal crusade out of removing
unneeded and unjustified printks from the kernel before it really gets better
though...
Oh well, I a
Trying to boot a build of the latest BK on ia64 I see
a series of messages like this:
mm/memory.c:99: bad pgd e001feba4000.
mm/memory.c:99: bad pgd e001febac000.
mm/memory.c:99: bad pgd e001febc0d10.
mm/memory.c:105: bad pmd f000eef3f200.
mm/memory.c:105: bad pmd f000eef3f000e2c3.
Hello,
my notebook have a SiS 964 Chipset and "quirked" by "quirk_sis_503", ... but
there is no SMbus device. If I add a call to the "quirk_sis_96x_smbus" function
directly from the "quirk_sis_503" function, the smbus is present, but I think a
call to a quirk from a quirk is not optimal. Is the
Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2005-03-10 at 17:47, Andrew Morton wrote:
> > Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> > >
> > > So, why is these slab cache are not getting purged/shrinked even
> > > under memory pressure ? (I have seen lowmem as low as 6MB). What
> >
On Mon, 2005-03-14 at 13:50 -0800, David S. Miller wrote:
> On Mon, 14 Mar 2005 13:14:43 -0800
> Dave Hansen <[EMAIL PROTECTED]> wrote:
>
> > Three of these are i386-only, but one of them reorganizes the macros
> > used to manage the space in page->flags, and will affect all platforms.
> > There a
On Sun, Mar 13, 2005 at 09:54:41AM +0100, Sam Ravnborg wrote:
> On Thu, Mar 10, 2005 at 12:12:22PM +, Paulo Marques wrote:
> > Paulo Marques wrote:
> > >[...]
> > >A simple and robust way is to do the sampling on a list of symbols
> > >sorted by symbol name. This way, even if the symbol positi
On Thu, Mar 10, 2005 at 09:25:54AM +0100, Andreas Gruenbacher wrote:
> On Wed, 2005-03-09 at 19:53, Justin M. Forbes wrote:
> > With the new stable series kernels, the .x versioning is being added to
> > EXTRAVERSION. This has traditionally been a space for local modification.
> > I know several d
Jake Moilanen writes:
> > I don't think I can push that upstream. What happens if you leave
> > that out?
>
> The bss and the plt are in the same segment, and plt obviously needs to
> be executable.
Yes... what I was asking was "do things actually break if you leave
that out, or does the binfmt
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 .te
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
lin
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: ./drivers/isdn/hisax/sed
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 refer
On Monday 14 March 2005 22:54, Brice Goglin wrote:
> DRM/i915 does not work on my Dell Dimension 3000 (i865 chipset).
> It's the first -mm kernel I try on this box. I don't whether previous -mm
> worked or not. Anyway, 2.6.11 works great.
You may want to try compiling without CONFIG_4KSTACKS. I've
On Mon, 14 Mar 2005 14:18:31 -0800
Dave Hansen <[EMAIL PROTECTED]> wrote:
> Those bits are used today for page_zone() and page_to_nid(). I assume
> that you don't support NUMA, but how do you get around the page_zone()
> definition? (a quick grep in asm-sparc64 didn't show anything obvious)
>
>
Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2005-03-14 at 14:11, Andrew Morton wrote:
> > Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> > >
> > > On Thu, 2005-03-10 at 17:47, Andrew Morton wrote:
> > > > Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > So, why is these sl
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 .te
On Mon, Mar 14, 2005 at 08:57:52AM +0100, Eric Piel wrote:
> BTW, DaveJ, Dominik, I couldn't find them in the daily-snapshot
> available at codemonkey.org.uk. Should I worry, or is it just due to
> some latency between your private trees and the public one?
/me has no official position wrt cpufr
On Thu, Mar 10, 2005 at 12:12:22PM +, Paulo Marques wrote:
> Paulo Marques wrote:
> >[...]
> >A simple and robust way is to do the sampling on a list of symbols
> >sorted by symbol name. This way, even if the symbol positions that are
> >given to scripts/kallsyms change, the symbols sampled w
On Wed, Mar 09, 2005 at 03:06:38AM -0500, Ryan Anderson wrote:
> Automatically append a semi-random version if the tree we're building
> isn't tagged in BitKeeper and CONFIG_LOCALVERSION_AUTO is set.
>
> This fixes the case when Linus (or someone else) does a release and tags
> it, someone else do
On Mon, 14 Mar 2005 14:06:09 -0800
"Luck, Tony" <[EMAIL PROTECTED]> wrote:
> Trying to boot a build of the latest BK on ia64 I see
> a series of messages like this:
>
> mm/memory.c:99: bad pgd e001feba4000.
> mm/memory.c:99: bad pgd e001febac000.
> mm/memory.c:99: bad pgd e001febc0d10
On Thu, 17 Feb 2005, Guennadi Liakhovetski wrote:
> Hello
>
> On Thu, 17 Feb 2005 [EMAIL PROTECTED] wrote:
>
> > > I believe there's unresolved memory corruption bug in bttv...
> > yes I think so, other have also similar problem :
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=11082080401020
On Mon, 2005-03-14 at 14:11, Andrew Morton wrote:
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, 2005-03-10 at 17:47, Andrew Morton wrote:
> > > Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> > > >
> > > > So, why is these slab cache are not getting purged/shrinked even
> > > > under
On Sun, Mar 13, 2005 at 04:59:14PM -0600, Corey Minyard wrote:
> Greg KH wrote:
> >On Sat, Mar 12, 2005 at 10:57:24PM -0600, Corey Minyard wrote:
> >>The IPMI driver has long needed to tie into the device model (and I've
> >>long been hoping someone else would do it). I finally gave up and spent
(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 for
Bernhard Rosenkraenzer a écrit :
On Monday 14 March 2005 22:54, Brice Goglin wrote:
DRM/i915 does not work on my Dell Dimension 3000 (i865 chipset).
It's the first -mm kernel I try on this box. I don't whether previous -mm
worked or not. Anyway, 2.6.11 works great.
You may want to try compiling wi
On Mon, 14 Mar 2005, Albert Cahalan wrote:
> On Mon, 2005-03-14 at 10:42 +0100, Rene Scharfe wrote:
> > Albert Cahalan wrote:
> > Why do you think users should not be allowed to chmod their processes'
> > /proc directories? Isn't it similar to being able to chmod their home
> > directories? Th
"Randy.Dunlap" <[EMAIL PROTECTED]> wrote:
>
> - "invalid count value %x %x \n", count, bufsiz);
> + "invalid count value %x %lx\n", count, (unsigned
> long)bufsiz);
Nope. Please use %Z for size_t args.
-
To unsubscribe from this list: send the line "unsubs
mà den 14.03.2005 Klokka 13:43 (-0800) skreiv Matt Mackall:
> On Mon, Mar 14, 2005 at 10:14:17AM +0100, Vegard Lima wrote:
> > Hello,
> >
> > in the long thread on "[request for inclusion] Realtime LSM" there
> > doesn't appear to be too many people who has actually tested the
> > nice-and-rt-prio
On Mon, 14 Mar 2005 14:34:42 -0800
"David S. Miller" <[EMAIL PROTECTED]> wrote:
> On Mon, 14 Mar 2005 14:06:09 -0800
> "Luck, Tony" <[EMAIL PROTECTED]> wrote:
>
> > Trying to boot a build of the latest BK on ia64 I see
> > a series of messages like this:
> >
> > mm/memory.c:99: bad pgd e001f
On Mon, 14 Mar 2005, comsatcat wrote:
>
> Is the qla2xxx dirver not capable of fail over support? under
> Documentation/* for the qla2xxx release notes, it says in a earlier
> revision that fail over was made optional. Was the optional support
> removed? If it is capable of fail over, what are
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
Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> sub make_message_id
> {
> my $date = `date "+\%s"`;
> chomp($date);
> my $pseudo_rand = int (rand(4200));
> $message_id = "<[EMAIL PROTECTED]>";
> print "new message id = $message_id\n";
> }
Why not
use Email::MessageID;
use Net::Domain qw(hostfqdn);
su
On Mon, Mar 14, 2005 at 09:06:26PM +0100, Stefan Roas wrote:
> On Mon Mar 14, 2005 at 18:24:44, Ben Dooks wrote:
>
> > This patch looks suspiciously like it is sweeping the problem
> > `under the carpet`. Does bus_to_virt() return an `void __iomem *`?
> >
> > reply should really be an `void __iom
The third edition of Linux Device drivers (by me, Alessandro Rubini, and
Greg Kroah-Hartman) is now available online:
http://lwn.net/Kernel/LDD3/
For the moment, it is only available in PDF format. The HTML and
DocBook versions will be posted once we have them in shape.
This edition is
Hi Dave,
I can't remove the AGP chipset module on my boxes.
Looks like the AGP chipset driver holds a reference on itself and
thus makes removal impossible.
From what I understand, as soon as intel_agp is loaded, agp_intel_probe
is called. It gets a reference on intel_agp module through
!try_module
On Mon, 14 Mar 2005 15:11:42 -0800
"David S. Miller" <[EMAIL PROTECTED]> wrote:
> I therefore suspect the pgwalk patches.
I just noticed something else while reviewing this stuff.
The PTRS_PER_PMD macros aren't used anymore, so my hacks
to get 32-bit process VM operations optimized on sparc64
are
john stultz wrote:
On Sat, 2005-03-12 at 16:49 -0800, Matt Mackall wrote:
~
+ /* finally, update legacy time values */
+ write_seqlock_irqsave(&xtime_lock, x_flags);
+ xtime = ns2timespec(system_time + wall_time_offset);
+ wall_to_monotonic = ns2timespec(wall_time_offset);
Pavel Machek wrote:
Hi!
And more... That this occures implies we are attempting to update the cmos
clock on resume seems wrong. One would presume that the time is wrong at
this
time and we are about to save that wrong time. Possibly the APM code
should
change time_status to STA_UNSYNC on the w
Hi Andrew/Tony
This patch is required for IPF to perform deferred write to rte's when
affinity is programmed via /proc. These entries can only be programmed when
interrupt is pending.
We will eventually need the same method for x86 and x86_64 as well.
This patch is only for IPF though. (the ot
Hi!
> > We already have the 'quiet' option, but even so, I think the kernel is
> > *way*
> > too verbose. Someone needs to make a personal crusade out of removing
> > unneeded and unjustified printks from the kernel before it really gets
> > better
> > though...
>
> Oh well, I admit going b
Ashok Raj <[EMAIL PROTECTED]> wrote:
>
> Hi Andrew/Tony
>
> This patch is required for IPF to perform deferred write to rte's when
> affinity is programmed via /proc. These entries can only be programmed when
> interrupt is pending.
"ia64" is preferred, please. Nobody knows what an IPF is.
>
(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 fi
(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.
(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:
undefined
On Fri, 11 Mar 2005, john stultz wrote:
> +/* get_lowres_timestamp():
> + * Returns a low res timestamp.
> + * (ie: the value of system_time as calculated at
> + * the last invocation of timeofday_periodic_hook() )
> + */
> +nsec_t get_lowres_timestamp(void)
> +{
> + nsec_t ret;
> +
You have to ignore the partition table contents for ending cylinder. Use
the following instead. You also
have to write your own FS or modify the partition code in Linux or you
won't be able to use the storage. This
config option listed in the previous post only enables 64 bit LBA
addressing, it
Hi!
> >>I agree. Still in all that follows, no one has addressed the apparent
> >>race described above. The reason the system reported the errors that
> >>started this thread is that the APM restore code was trying to read the
> >>cmos clock (I assume to set the xtime clock) WHILE the timer i
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 a patch for
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 a patc
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 in the mtd
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 in t
On Mon, Mar 14, 2005 at 03:59:23PM -0800, Andrew Morton wrote:
> Ashok Raj <[EMAIL PROTECTED]> wrote:
> >
>
> "ia64" is preferred, please. Nobody knows what an IPF is.
Right!. Sorry about that.
>
>
> Is it not possible for ia64's ->set_affinity() handler to do this deferring?
>
There are oth
I get this output with current Linus bk :
[0.00] Total memory = 512MB; using 1024kB for hash table (at 8040)
[0.00] Linux version 2.6.11-gack ([EMAIL PROTECTED]) (gcc version 3.3.5
(Debian 1:3.3.5-8)) #5 Tue Mar 15 11:20:41 EST 2005
[0.00] Found UniNorth memory contro
Hello IDE experts.
I am trying to use a SanDisk SDCFB-256, CFA DISK drive. This
is supposed to emulate an IDE drive and does (sort of). However,
upon boot, the boot-code keeps trying and trying and trying to
do SOMETHING that aparently isn't even necessary because the
virtual disk is accessible and
On Mon, 14 Mar 2005, john stultz wrote:
> Huh. So if I understand you properly, all timesources should have valid
> read_fnct pointers that return the cycle value, however we'll still
> preserve the type and mmio_ptr so fsyscall/vsyscall bits can use them
> externally?
>
> Hmm. I'm a little cautio
(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 ./fs/reiser
On Sat, Mar 12, 2005 at 02:14:50AM -0800, Junfeng Yang wrote:
>
> Hi,
>
> We are from the Stanford Checker team and are working on a file system
> checker called FiSC. We checked XFS and found that even when a XFS
> partition is mounted -o sync, file system operations are still not sync'ed
> cor
A quick skim...
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
> + *
> + * inode.c
> + */
> +
> +#include
> +#include
> +#include
On Mon, 14 Mar 2005 08:40:22 -0500, Stephen Evanchik <[EMAIL PROTECTED]> wrote:
> On Mon, 14 Mar 2005 13:19:56 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > How much does it interpret the stream in non-transparent mode? Are
> > commands also passed through in soft transparent mode?
> >
> > I
On Mon, 2005-03-14 at 16:28 -0800, Christoph Lameter wrote:
> On Mon, 14 Mar 2005, john stultz wrote:
>
> > Huh. So if I understand you properly, all timesources should have valid
> > read_fnct pointers that return the cycle value, however we'll still
> > preserve the type and mmio_ptr so fsyscall
On Mon, 14 Mar 2005, Matt Mackall wrote:
> We can either stick all the generic mmio timer functions in the
> vsyscall page (they're tiny) or leave the vsyscall using type/ptr but
> have the kernel internally use only the function pointer. Someone
> who's more familiar with the vsyscall timer code s
Hi just see that the whole stack of pmac SWSUSP patches went in, without
any notice nor CC nor anything from any of the PPC maintainers ! That is
a bit annoying don't you think ?
Paulus and I wrote most of those patches, granted, and they've been
hanging around for some time, but I had good reason
Phillip Lougher <[EMAIL PROTECTED]> wrote:
>
> Please apply the following two patches which adds SquashFS to the
> kernel.
> +
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
>
On Mon, Mar 14, 2005 at 11:32:39AM -0800, Jesse Barnes wrote:
> The sal_console and sal_console_uart structures have a circular relationship
> since they both initialize member fields to pointers of one another. The
> current code forward declares sal_console_uart as extern so that sal_console
On Tue, Mar 15, 2005 at 12:28:51AM +0100, Brice Goglin wrote:
> Hi Dave,
>
> I can't remove the AGP chipset module on my boxes.
> Looks like the AGP chipset driver holds a reference on itself and
> thus makes removal impossible.
>
> From what I understand, as soon as intel_agp is loaded, a
Phillip Lougher <[EMAIL PROTECTED]> wrote:
>
>
Please don't send multiple patches with the same Subject:. Choose nice,
meaningful Subject:s for each patch. And include the relevant changelog
details within the email for each patch rather than in patch 1/N. See
http://www.zip.com.au/~akpm/linux
On Mon, 2005-03-14 at 15:40 -0800, George Anzinger wrote:
> john stultz wrote:
> > On Sat, 2005-03-12 at 16:49 -0800, Matt Mackall wrote:
> >>>+ /* finally, update legacy time values */
> >>>+ write_seqlock_irqsave(&xtime_lock, x_flags);
> >>>+ xtime = ns2timespec(system_time + wall_time_offset)
201 - 300 of 388 matches
Mail list logo
