Remove from the documentation the notion of using "depends" rather
than "depends on" in Kconfig files.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
given that there are only three Kconfig files left that still use
"depends" rather than "depends on", there's no point encouraging
a
On 12/17/06, D. Hazelton <[EMAIL PROTECTED]> wrote:
On Sunday 17 December 2006 16:32, David Schwartz wrote:
> > I would argue that this is _particularly_ pertinent with regards to
> > Linux. For example, if you look at many of our atomics or locking
> > operations a good number of them (dependin
On Monday 18 December 2006 10:45, Stefan Richter wrote:
>Gene Heskett wrote:
>> On Sunday 17 December 2006 20:05, Stefan Richter wrote:
>>>What's missing in our implementation is that the use count of ohci1394
>>>goes up too once a "high-level driver" uses resources of a host driven
>>>by ohci1394.
an allyesconfig bootup generates the driver core warning below, in
alsa_card_dummy_init().
Ingo
-->
Calling initcall 0xc1ee1d35: alsa_card_dummy_init+0x0/0x8a()
PM: Adding info for platform:snd_dummy.0
kobject_add failed for audio with -EEXIST, don't try to register thin
allyesconfig bzImage bootup produced 33 warning messages, of which the
first couple are attached below.
Ingo
--->
Calling initcall 0xc0628d59: isicom_setup+0x0/0x315()
kobject_add failed for ttyM0 with -EEXIST, don't try to register things with
the same name in the same dir
kernel-parameters.txt says what ACPI and APM stand for, but not APIC.
Also there give some basic apm related parameters, instead of just
saying see apm.c, which the user is less likely to have handy than
kernel-parameters.txt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
I'd never have noticed an issue if I hadn't looked in the dmesg for something
else, so it isn't a high-priority item.. I admit being fuzzy on what, if
anything, even *actually* needs fixing (ISTR for some people, there was some
config issue with the transparent bridges being only translucent, but
(Yes, I *know* the answer is probably "Get Dell to fix the BIOS settings",
but I'll need some more info on exactly what to tell them so it gets fixed
right.
Scenario - I recently got a Dell Latitude D820 to replace my aging C840.
Am running Fedora Core Rawhide in (mostly) 64-bit mode.
Folly 1: I
In-Reply-To: <[EMAIL PROTECTED]>
On Mon, 18 Dec 2006 09:17:32 +0200, Ava Kivity wrote:
> In 2.6.20-rc1, some of these files have other files with the same name
> in the same directory (modulo case). Perhaps this is confusing cifs.
>
> Can you check where all of the files in your case share tha
On Mon, 2006-12-18 at 16:53 +0100, Ingo Molnar wrote:
> an allyesconfig bootup generates the driver core warning below, in
> alsa_card_dummy_init().
>
> Ingo
>
> -->
> Calling initcall 0xc1ee1d35: alsa_card_dummy_init+0x0/0x8a()
> PM: Adding info for platform:snd_dummy.0
>
On Mon, Dec 18, 2006 at 10:40:25AM -0500, Robert P. J. Day wrote:
>
> Remove from the documentation the notion of using "depends" rather
> than "depends on" in Kconfig files.
>
> Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
>
> ---
>
> given that there are only three Kconfig files le
Hi,
Recently my mysql servershows something like:
Dec 18 18:24:05 sql kernel: schedule_timeout: wrong timeout value
from c0284efd
Dec 18 18:24:36 sql last message repeated 19939 times
Dec 18 18:25:37 sql last message repeated 33392 times
from syslog every 1 or 2 days. Whenever the mes
On Mon, 2006-12-18 at 16:31 +0100, Ingo Molnar wrote:
> crash in adummy_init() - allyesconfig bootup.
>
> Ingo
>
> >
> Calling initcall 0xc1eb1f7e: adummy_init+0x0/0xb9()
> adummy: version 1.0
> swapper/1[CPU#0]: BUG in kref_get at lib/kref.c:32
> [] show_trace_log_lvl+0x34
On Mon, 2006-12-18 at 11:13 -0500, Chuck Ebbert wrote:
> With cifs, a directory search shows different sizes but opening
> them by name gives identical contents:
>
> $ ll ipt_dscp* ipt_DSCP*
> -r 1 me me 1581 Jan 28 2004 ipt_dscp.c
> -r 1 me me 2753 Jan 29 2004 ipt_DSCP.c
> $ ll
On Mon, 18 Dec 2006, Adrian Bunk wrote:
> On Mon, Dec 18, 2006 at 10:40:25AM -0500, Robert P. J. Day wrote:
> >
> > Remove from the documentation the notion of using "depends" rather
> > than "depends on" in Kconfig files.
> >
> > Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
> >
> > ---
>
Remove the note in the documentation that suggests people can use
"requires" for dependencies in Kconfig files.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
at this point, AFAICT, all Kconfig files now use "depends on"
exclusively, except for three that still use "depends", but i
[EMAIL PROTECTED] writes:
> http://bugzilla.kernel.org/show_bug.cgi?id=7505
>
> --- Additional Comments From [EMAIL PROTECTED] 2006-12-18 07:39 ---
> OK, fixed.
Greg.
It appears commit d71374dafbba7ec3f67371d3b7e9f6310a588808 which
replaced the pci bus spinlock with a semaphore causes
On Sun, 2006-12-17 at 15:40 -0800, Andrew Morton wrote:
> On Sun, 17 Dec 2006 15:39:32 +0200
> Andrei Popa <[EMAIL PROTECTED]> wrote:
>
> > I was mistaken, I'm still having file corruption with rtorrent.
> >
>
> Well I'm not very optimistic, but if people could try this, please...
>
>
>
> Fro
Ingo Molnar wrote:
> allyesconfig bzImage bootup produced 33 warning messages, of which the
> first couple are attached below.
With which kernel? mxser had ttyM for a long time, it should be fixed in
2.6.20-rc1.
> --->
> Calling initcall 0xc0628d59: isicom_setup+0x0/0x315()
> kobje
On Mon, Dec 18, 2006 at 10:38:38AM -0500, Dave Neuer wrote:
> I think this is the key, both with libraries and w/ your book example
> below; the concept of independant "meaning." If your code doesn't do
> whatever it is supposed to do _unless_ it is linked with _my_ code,
> then it seems fairly cle
Rafael J. Wysocki wrote:
> Hi,
>
> On Monday, 18 December 2006 12:20, Jiri Slaby wrote:
>> Hi.
>>
>> I got this oops while suspending:
>> [ 309.366557] Disabling non-boot CPUs ...
>> [ 309.386563] CPU 1 is now offline
>> [ 309.387625] CPU1 is down
>> [ 309.387704] Stopping tasks ... done.
>> [
Combined responses to save bandwidth and reduce the number of times people
have to press "d".
> Agreed. You missed the point.
I don't understand how you could lead with "agreed" and then proceed to
completely ignore the entire point I just made.
> Since the Linux Kernel header files
> contain a
On 12/18/06, Theodore Tso <[EMAIL PROTECTED]> wrote:
On Mon, Dec 18, 2006 at 10:38:38AM -0500, Dave Neuer wrote:
> I think this is the key, both with libraries and w/ your book example
> below; the concept of independant "meaning." If your code doesn't do
> whatever it is supposed to do _unless_
Randy Dunlap wrote:
On Fri, 15 Dec 2006 23:46:28 -0500 Mike Accetta wrote:
After upgrading an NFS client from 2.6.18 to 2.6.19 (and also with
2.6.19.1) we see a change in behavior of multiple NFS mounts against the
same server (running 2.4.20 in this case). With 2.6.18 we could mount
differe
Eric W. Biederman wrote:
Things we can say without being hypocrites and without getting into
legal theory:
Kernel modules without source, or that don't have a GPL compatible
license are inconsiderate and rude.
??
Please don't be rude.
???
J
Eric
-
To unsubscribe from
On Sat, 11 Nov 2006 11:03:51 +0100 Miguel Ojeda wrote:
> David, as akpm suggested, may this patch will solve the dcache aliasing
> problem?
>
> I will give you a introduction:
>
> The user mmaped page (got by __get_free_page()) is cfag12864b_buffer.
>
> The kernel only access it for reading at
In 2.6.20-rc1-mm1, with HOTPLUG=n, 2 linux/kobject.h inline functions
need to return . Currently this causes 962 warnings like this:
include/linux/kobject.h: In function 'kobject_uevent':
include/linux/kobject.h:277: warning: no return statement in function returning
non-void
include/linux/kobj
Add a new section to the CodingStyle file, encouraging people not to
re-invent available kernel macros such as ARRAY_SIZE(),
FIELD_SIZEOF(), min() and max(), among others.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
NOTE: at the moment, there is not a single invocation of the
F
Almost exactly 24 hours after booting 2.6.19.1-rt15, I encountered the
following:
softirq-tasklet/49[CPU#3]: BUG in __tasklet_action at kernel/softirq.c:568
Call Trace:
[] __WARN_ON+0x5c/0x74
[] __tasklet_action+0xae/0xf2
[] ksoftirqd+0xfc/0x198
[] ksoftirqd+0x0/0x198
[] kthread+0xd1/0x101
[] ch
On Mon, 18 Dec 2006 12:43:35 -0500 (EST) Robert P. J. Day wrote:
>
> Add a new section to the CodingStyle file, encouraging people not to
> re-invent available kernel macros such as ARRAY_SIZE(),
> FIELD_SIZEOF(), min() and max(), among others.
>
> Signed-off-by: Robert P. J. Day <[EMAIL PROTE
Andrei,
could you try Peter's patch (on top of Andrew's patch - it depends on
it, and wouldn't work on an unmodified -git kernel, but add the WARN_ON()
I mention in this email? You seem to be able to reproduce this easily..
Thanks)
On Mon, 18 Dec 2006, Peter Zijlstra wrote:
>
> This should b
The patch below fixes a bug that only appears when AoE goes over a
network card that does not support scatter-gather. The headers in the
linear part of the skb appeared to be larger than they really were,
resulting in data that was offset by 24 bytes.
This patch eliminates the offset data on card
Willy,
I'm forwarding this over to linux-scsi@vger.kernel.org because it seems
that [EMAIL PROTECTED] was discontinued a few years ago.
Maybe the folks over there will be able to shed some light on this bug.
Mark.
On Sat, 2006-12-16 at 00:03 +0100, Willy Tarreau wrote:
> Hello Mark,
>
> On Thu,
On Mon, 2006-12-18 at 10:03 -0800, Linus Torvalds wrote:
> Andrei,
> could you try Peter's patch (on top of Andrew's patch - it depends on
> it, and wouldn't work on an unmodified -git kernel, but add the WARN_ON()
> I mention in this email? You seem to be able to reproduce this easily..
> Than
On Sat, Dec 16 2006, Linus Torvalds wrote:
> That said: Jens - I think 0e75f906 was a mistake. "blk_rq_unmap()" really
> should be passed the "struct bio", not the "struct request *". Right now
> it does something _really_ strange with requests with linked bio's, and I
> don't think your and FUJ
Wiebe Cazemier wrote:
When using non-identical discs (not just size, but also geometry) to contruct
your array, you can never get the partitions of the underlying discs to be
equal in size because the size of a partition can only be N*cylindersize,
where cylindersize varies across discs; the arra
On Mon, 18 Dec 2006, Peter Zijlstra wrote:
> >
> > Or maybe the WARN_ON() just points out _why_ somebody would want to do
> > something this insane. Right now I just can't see why it's a valid thing
> > to do.
>
> Maybe, but I think Nick's mail here:
> http://lkml.org/lkml/2006/12/18/59
>
> > > The reiser4 failure is unexpected. Could you please see if you can
> > > capture a trace, let the people at [EMAIL PROTECTED] know?
> > Ok, I've handwritten the messages, here they are :
> > reiser4 panicked cowardly : reiser4[umount(2451)] : commit_current_atom
> > (fs/reiser4/txmngr.c:10
On Mon, Dec 18 2006, Jens Axboe wrote:
> On Sat, Dec 16 2006, Linus Torvalds wrote:
> > That said: Jens - I think 0e75f906 was a mistake. "blk_rq_unmap()" really
> > should be passed the "struct bio", not the "struct request *". Right now
> > it does something _really_ strange with requests with
Miles Lane wrote:
> Sorry, I am not finding who maintains highmem. Please forward.
>
> WARNING (1) at arch/i386/mm/highmem.c:41 kmap_atomic()
> [] dump_trace+0x68/0x1d2
> [] show_trace_log_lvl+0x18/0x2c
> [] show_trace+0xf/0x11
> [] dump_stack+0x12/0x14
> [] kmap_atomic+0x6f/0x1ca
> [] ntfs_end_b
hi,
while playing around with fsfuzzer, i got the following oops with jfs:
[ 851.804875] BUG at fs/jfs/jfs_xtree.c:760 assert(!BT_STACK_FULL(btstack))
[ 851.805179] [ cut here ]
[ 851.805238] kernel BUG at fs/jfs/jfs_xtree.c:760!
[ 851.805287] invalid opcode: [#1]
On 12/18/06, Jiri Slaby <[EMAIL PROTECTED]> wrote:
Miles Lane wrote:
> Sorry, I am not finding who maintains highmem. Please forward.
>
> WARNING (1) at arch/i386/mm/highmem.c:41 kmap_atomic()
> [] dump_trace+0x68/0x1d2
> [] show_trace_log_lvl+0x18/0x2c
> [] show_trace+0xf/0x11
> [] dump_stack+0
> (On that note: Andrei - if you do test this out, I'd suggest applying my
> patch too - the one that you already tested. It won't apply cleanly on top
> of Andrew's patch, but it should be trivial to apply by hand, since you
> really just want to remove the whole "if (ret) {...}" sequence. I r
From: Ingo Molnar <[EMAIL PROTECTED]>
Subject: [patch] workqueue: fix schedule_on_each_cpu()
fix the schedule_on_each_cpu() implementation: __queue_work() is now
stricter, hence set the work-pending bit before passing in the new work.
(found in the -rt tree, using Peter Zijlstra's files-lock scal
Miles Lane wrote:
> On 12/18/06, Jiri Slaby <[EMAIL PROTECTED]> wrote:
>> Miles Lane wrote:
>> > Sorry, I am not finding who maintains highmem. Please forward.
>> >
>> > WARNING (1) at arch/i386/mm/highmem.c:41 kmap_atomic()
>> > [] dump_trace+0x68/0x1d2
>> > [] show_trace_log_lvl+0x18/0x2c
>> > [
On Mon, 2006-12-18 at 21:04 +0200, Andrei Popa wrote:
> diff --git a/mm/rmap.c b/mm/rmap.c
> index d8a842a..3f9061e 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -448,7 +448,7 @@ static int page_mkclean_one(struct page
> goto unlock;
>
> entry = ptep_get_and_clear(mm, addr
On Mon, 18 Dec 2006, Andrei Popa wrote:
>
> I applied Linus patch, Andrew patch, Peter Zijlstra patches(the last
> two). All unified patch is attached. I tested and I have no corruption.
That wasn't very interesting, because you also had the patch that just
disabled "page_mkclean_one()" entire
On Dec 17, 2006, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> For example, glibc could easily have just come out and said the thing that
> is obvious to any sane person: "using this library as just a standard
> library does not make your program a derived work".
> There really wassn't much need
On Dec 17, 2006, Kyle Moffett <[EMAIL PROTECTED]> wrote:
> On the other hand, certain projects like OpenAFS, while not license-
> compatible, are certainly not derivative works.
Certainly a big chunk of OpenAFS might not be, just like a big chunk
of other non-GPL drivers for Linux.
But what abo
I have a question I could not quickly find on Google/mailing lists--
Say I have some sort of global filesystem or NFS which is 200TB.
Is there a limit either:
A) In the Linux kernel
or
B) In the NFS spec
That would limit the client as to what it could see via NFS or global
filesystem?
Or coul
On Mon, 18 Dec 2006, Alexandre Oliva wrote:
>
> So I guess you approve of the reformulation of LGPL as an additional
> permission on top of GPL, as in its draft at gplv3.fsf.org, right?
Yes. I think that part of the GPLv3 is a good idea.
That said, I think they are still pushing the "you don't
On Mon, 2006-12-18 at 11:18 -0800, Linus Torvalds wrote:
>
> On Mon, 18 Dec 2006, Andrei Popa wrote:
> >
> > I applied Linus patch, Andrew patch, Peter Zijlstra patches(the last
> > two). All unified patch is attached. I tested and I have no corruption.
>
> That wasn't very interesting, because
>kernel-parameters.txt says what ACPI and APM stand for, but not APIC.
Advanced PIC, most likely. http://en.wikipedia.org/wiki/APIC will tell
more.
>Also there give some basic apm related parameters, instead of just
>saying see apm.c, which the user is less likely to have handy than
>kernel-par
Replace kmalloc() + memset() pairs with the appropriate kzalloc()
calls.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
i could have sworn i submitted this patch a while back but it
doesn't seem to have been applied. it's possible it's still in the
queue somewhere but it seems unl
* Catalin Marinas <[EMAIL PROTECTED]> wrote:
> >at freeing we only have to look up the tree belonging to object->cpu.
>
> At freeing, kmemleak only gets a pointer value which has to be looked
> up in the hash table for the corresponding memleak_object. Only after
> that, we can know memleak_ob
* Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> > allyesconfig bzImage bootup produced 33 warning messages, of which the
> > first couple are attached below.
>
> With which kernel? mxser had ttyM for a long time, it should be fixed
> in 2.6.20-rc1.
current -git.
Ingo
-
Ingo Molnar wrote:
> * Jiri Slaby <[EMAIL PROTECTED]> wrote:
>
>> Ingo Molnar wrote:
>>> allyesconfig bzImage bootup produced 33 warning messages, of which the
>>> first couple are attached below.
>> With which kernel? mxser had ttyM for a long time, it should be fixed
>> in 2.6.20-rc1.
>
> cur
On 12/15/06, Andrew Morton <[EMAIL PROTECTED]> wrote:
+toshiba-tc86c001-ide-driver-take-2.patch
Acked-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
IMO this can be merged for 2.6.20 as it is new driver
(which is clean, tested and acked by Alan already)
All 693 patches:
hpt3xx-rework-r
On Mon, 2006-12-18 at 14:21 -0500, Justin Piszcz wrote:
> I have a question I could not quickly find on Google/mailing lists--
>
> Say I have some sort of global filesystem or NFS which is 200TB.
>
> Is there a limit either:
>
> A) In the Linux kernel
> or
> B) In the NFS spec
>
> That would li
On Mon, Dec 18, 2006 at 02:53:05PM -0500, Robert P. J. Day wrote:
>
> Replace kmalloc() + memset() pairs with the appropriate kzalloc()
> calls.
>
> Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
>
> ---
>
> i could have sworn i submitted this patch a while back but it
> doesn't seem t
Thanks for the info!
On Mon, 18 Dec 2006, Trond Myklebust wrote:
> On Mon, 2006-12-18 at 14:21 -0500, Justin Piszcz wrote:
> > I have a question I could not quickly find on Google/mailing lists--
> >
> > Say I have some sort of global filesystem or NFS which is 200TB.
> >
> > Is there a limit e
On Mon, Dec 18, 2006 at 09:49:24AM -0800, Randy Dunlap wrote:
> In 2.6.20-rc1-mm1, with HOTPLUG=n, 2 linux/kobject.h inline functions
> need to return . Currently this causes 962 warnings like this:
>
> include/linux/kobject.h: In function 'kobject_uevent':
> include/linux/kobject.h:277: warning:
On Mon, 18 Dec 2006, Andrei Popa wrote:
>
> I dropped that patch and added WARN_ON(1), the unified patch is
> attached.
>
> I got corruption: "Hash check on download completion found bad chunks,
> consider using "safe_sync"."
Ok. That is actually _very_ interesting.
It's interesting because (
On top of "[PATCH, RFC] reimplement flush_workqueue()", see
http://marc.theaimsgroup.com/?l=linux-kernel&m=116639510029010
Andrew Morton wrote:
>
> A basic problem with flush_scheduled_work() is that it blocks behind _all_
> presently-queued works, rather than just the work whcih the calle
> Add a new section to the CodingStyle file, encouraging people not to
>re-invent available kernel macros such as ARRAY_SIZE(),
>FIELD_SIZEOF(), min() and max(), among others.
>
>Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
Acked-by: Jan Engelhardt <[EMAIL PROTECTED]>
-`J'
--
-
On 12/18/06, Randy Dunlap <[EMAIL PROTECTED]> wrote:
Hi,
Shouldn't the framebuffer part of this code (cfag12864bfb) also
depend on CONFIG_FB? Without that, this build error occurs:
Indeed it should. Thanks for noticing that!
cfag12864bfb.c:(.init.text+0xc19d): undefined reference to `fram
Dmitriy Monakhov wrote on Monday, December 18, 2006 5:23 AM
> This patch is result of discussion started week ago here:
> http://lkml.org/lkml/2006/12/11/66
> changes from original patch:
> - Update wrong comments about i_mutex locking.
> - Add BUG_ON(!mutex_is_locked(..)) for non blkdev.
> - v
Ingo Molnar wrote:
> * Jiri Slaby <[EMAIL PROTECTED]> wrote:
>
>> Ingo Molnar wrote:
>>> allyesconfig bzImage bootup produced 33 warning messages, of which the
>>> first couple are attached below.
>> With which kernel? mxser had ttyM for a long time, it should be fixed
>> in 2.6.20-rc1.
>
> cur
Hi !
I have a phenomena that I don't quite understand. gdbserver forks and
after setting ptrace (PTRACE_TRACEME, 0, 0, 0); it then execv
(program, allargs); when this child process hits ptrace_stoped (breakpoint
it does the following in kernel space:
pid 1242 = child process
pid 1241 = gdb
On Dec 18, 2006, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> That said, I think they are still pushing the "you don't have any rights
> unless we give you additional rights explicitly" angle a bit too hard.
Maybe it's just a matter of perception. I don't see it that way from
the inside.
How ab
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix inline kobject functions to return 0 when CONFIG_HOTPLUG=n.
include/linux/kobject.h: In function 'kobject_uevent':
include/linux/kobject.h:277: warning: no return statement in function returning
non-void
include/linux/kobject.h: In function 'kobject_uev
* Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> > * Jiri Slaby <[EMAIL PROTECTED]> wrote:
> >
> >> Ingo Molnar wrote:
> >>> allyesconfig bzImage bootup produced 33 warning messages, of which the
> >>> first couple are attached below.
> >> With which kernel? mxser had ttyM for a l
On Mon, 18 Dec 2006, Linus Torvalds wrote:
>
> But at the same time, it's interesting that it still happens when we try
> to re-add the dirty bit. That would tell me that it's one of two cases:
Forget that. There's a third case, which is much more likely:
- Andrew's patch had a ", 1" where i
On Mon, 2006-12-18 at 19:51 +0100, Eric Sesterhenn wrote:
> hi,
>
> while playing around with fsfuzzer, i got the following oops with jfs:
>
> [ 851.804875] BUG at fs/jfs/jfs_xtree.c:760 assert(!BT_STACK_FULL(btstack))
...
> On a damaged filesystem we might have a full stack and should
> not
On Mon, 18 Dec 2006, Alexandre Oliva wrote:
>
> > In other words, in the GPL, "Program" does NOT mean "binary". Never has.
>
> Agreed. So what? How does this relate with the point above?
>
> The binary is a Program, as much as the sources are a Program. Both
> forms are subject to copyright
On Monday 18 December 2006 10:47, Dave Neuer wrote:
> On 12/17/06, D. Hazelton <[EMAIL PROTECTED]> wrote:
> > On Sunday 17 December 2006 16:32, David Schwartz wrote:
> > > > I would argue that this is _particularly_ pertinent with regards to
> > > > Linux. For example, if you look at many of our a
On Mon, 18 Dec 2006 18:02:20 +0100
Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Monday, 18 December 2006 12:20, Jiri Slaby wrote:
> >> Hi.
> >>
> >> I got this oops while suspending:
> >> [ 309.366557] Disabling non-boot CPUs ...
> >> [ 309.386563] CPU 1 i
On 12/18/06, D. Hazelton <[EMAIL PROTECTED]> wrote:
Ah, okay. However I'm quite sure that there are more ways to accomplish the
tasks handled by the code in the header files (in most cases).
Well, that may be so. Unfortunately, Lexmark vs. Static Controls
actually says that even if there are o
Hi :o)
On Fri, 2006-12-15 at 18:55 -0800, Linus Torvalds wrote:
> But the point is, "derived work" is not what _you_ or _I_ define. It's
> what copyright law defines.
Of course not. I never suggested trying to define a derived work.
> And trying to push that definition too far is a total disast
On Mon, 2006-12-18 at 12:41 -0800, Linus Torvalds wrote:
>
> On Mon, 18 Dec 2006, Linus Torvalds wrote:
> >
> > But at the same time, it's interesting that it still happens when we try
> > to re-add the dirty bit. That would tell me that it's one of two cases:
>
> Forget that. There's a third c
On Sat, 2006-12-16 at 17:03 +0900, KAMEZAWA Hiroyuki wrote:
> /* add this memory to iomem resource */
> static struct resource *register_memory_resource(u64 start, u64 size)
> {
> @@ -273,10 +284,13 @@
> if (ret)
> goto error;
> }
> + atomic_inc(&mem
> Static vs dynamic matters for whether it's an AGGREGATE work. Clearly,
> static linking aggregates the library with the other program in the same
> binary. There's no question about that. And that _does_ have meaning from
> a copyright law angle, since if you don't have permission to ship
> aggr
On 12/18, Eric W. Biederman wrote:
>
> Oleg Nesterov <[EMAIL PROTECTED]> writes:
>
> > Btw, de_thread() already takes care about multithread init, but
> > get_signal_to_deliver() does not:
> >
> > if (current == child_reaper(current))
> > continue;
>
> Probably just: current->grou
On Mon, 18 Dec 2006 12:14:35 -0800 (PST)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> OR:
>
> - page_mkclean_one() is simply buggy.
>
> And I'm starting to wonder about the second case. But it all LOOKS really
> fine - I can't see anything wrong there (it uses the extremely
> conservative "pte
Kirill Korotaev wrote on Monday, December 18, 2006 4:05 AM
> [IA64] bug in ldscript (mainstream)
>
> Occasionally, in mainstream number of fsys entries is even.
Is it a typo on "fsys entries is even"?
If not, then this change log is misleading. It is the instruction
patch list of FSYS_RETURN tha
On Mon, Dec 18, 2006 at 12:43:35PM -0500, Robert P. J. Day wrote:
> Add a new section to the CodingStyle file, encouraging people not to
> re-invent available kernel macros such as ARRAY_SIZE(),
> FIELD_SIZEOF(), min() and max(), among others.
Good stuff. Could you also mention the printk() KERN
Alan wrote:
On Fri, 15 Dec 2006 11:50:14 -0500
Bill Davidsen <[EMAIL PROTECTED]> wrote:
Did I miss an alternate method of handling ftape devices, or are these
old beasts now unsupported? I occasionally have to be able to handle
that media, since the industrial device using ftape for control
On Mon, 2006-12-18 at 12:14 -0800, Linus Torvalds wrote:
>
> On Mon, 18 Dec 2006, Andrei Popa wrote:
> >
> > I dropped that patch and added WARN_ON(1), the unified patch is
> > attached.
> >
> > I got corruption: "Hash check on download completion found bad chunks,
> > consider using "safe_sync"
Marek Wawrzyczny wrote:
Dear Linux Kernel ML,
I am writing as a Linux-only user of over 2 years to express my concern with
the recent proposal to block out closed source modules from the kernel.
While, I understand and share your sentiments over open source software and
drivers. I fear howev
On Mon, 18 Dec 2006, Erik Mouw wrote:
> On Mon, Dec 18, 2006 at 12:43:35PM -0500, Robert P. J. Day wrote:
> > Add a new section to the CodingStyle file, encouraging people not to
> > re-invent available kernel macros such as ARRAY_SIZE(),
> > FIELD_SIZEOF(), min() and max(), among others.
>
> Go
On 12/18/06, Andrei Popa <[EMAIL PROTECTED]> wrote:
On Mon, 2006-12-18 at 12:41 -0800, Linus Torvalds wrote:
>
> On Mon, 18 Dec 2006, Linus Torvalds wrote:
> >
> > But at the same time, it's interesting that it still happens when we try
> > to re-add the dirty bit. That would tell me that it's on
On Mon, Dec 18, 2006 at 10:04:07PM +0100, karderio wrote:
> I have realised that the proposed changes do not *impose* any more
> restriction on the use of the kernel than currently exists. Currently
> the Kernel is licenced to impose the same licence on derived works,
> enforce distribution of sour
Use the appropriate logging macro for the priority level for that
printk call.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
this appears to be the only instance in the entire tree of
hard-coding the log level in a printk.
diff --git a/arch/ppc/syslib/m8260_pci_erratum9.c
b/arc
On Mon, 18 Dec 2006, karderio wrote:
>
> I don't see how what is proposed for blocking non GPL modules at all
> touches the definition of derived work. Even if according to law and the
> GPL, binary modules are legal, the proposed changes could still be
> made.
.. and then what does that mean?
On Mon, Dec 18, 2006 at 05:41:17PM -0200, Alexandre Oliva wrote:
> On Dec 17, 2006, Kyle Moffett <[EMAIL PROTECTED]> wrote:
>
> > On the other hand, certain projects like OpenAFS, while not license-
> > compatible, are certainly not derivative works.
>
> Certainly a big chunk of OpenAFS might no
On Mon, Dec 18, 2006 at 04:22:44PM +0300, Dmitriy Monakhov wrote:
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 8332c77..7c571dd 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -2044,8 +2044,9 @@ generic_file_direct_write(struct kiocb *
> /*
>* Sync the fs metadata but not
On Mon, Dec 18, 2006 at 01:13:57PM -0800, Dave Hansen wrote:
> On Sat, 2006-12-16 at 17:03 +0900, KAMEZAWA Hiroyuki wrote:
> > /* add this memory to iomem resource */
> > static struct resource *register_memory_resource(u64 start, u64 size)
> > {
> > @@ -273,10 +284,13 @@
> > if (ret
(This email is a followup to "Re: [PATCH 2.6.19.1] fix aoe without
scatter-gather [Bug 7662]".)
On Mon, Dec 18, 2006 at 12:53:00PM -0500, Ed L. Cashin wrote:
...
> This patch eliminates the offset data on cards that don't support
> scatter-gather or have had scatter-gather turned off. There remai
Linus Torvalds wrote:
On Mon, 18 Dec 2006, Alexandre Oliva wrote:
In other words, in the GPL, "Program" does NOT mean "binary". Never has.
Agreed. So what? How does this relate with the point above?
The binary is a Program, as much as the sources are a Program. Both
forms are sub
On Mon, Dec 18, 2006 at 08:41:33AM +, Willy Tarreau wrote:
> Hi,
>
> Two changes before -final. The first one fixes a race where
> one can hit a BUG(), the second one fixes CVE-2006-4814.
>
> -final is just a few days ahead (it scares me, I'll have to check
> my scripts to ensure everything'
101 - 200 of 335 matches
Mail list logo
