On Sat, Jun 09, 2007 at 11:05:07PM +0200, Ingo Molnar wrote:
>
> i'm pleased to announce the v2.6.21.4-rt11 kernel, which can be
> downloaded from the usual place:
>
> http://people.redhat.com/mingo/realtime-preempt/
>
> more info about the -rt patchset can be found in the RT wiki:
>
Alistair John Strachan wrote:
> On Sunday 10 June 2007 13:03:15 you wrote:
>
>>訳注(2)
>>「引火性の高い」の原文は "valatile"。
>>valatile には「揮発性の」「爆発しやすい」という意味の他、「変わり
>>やすい」「移り気な」という意味がある。
>>「（この話題は）爆発的に激しい論争を巻き起こしかねない」ということ
>>を、「（カーネルのソースレベルインターフェースは）移ろい行くもので
>>ある」ということを連想させる "valatile" という単語で表現している。
>
>
> No
Hi Richard!
On Sun, 10 Jun 2007, Richard Hughes wrote:
> On Sun, 2007-06-10 at 12:11 +0200, Pavel Machek wrote:
> > Can we keep the original naming? spitz:disk is as unique as led02, and
> > it is _way_ easier to use.
> > Come on, I want to use the led subsystem from the scripts...
>
> I don't
Matthew Garrett wrote:
> No, it only supports ext2 (and reading ext3 as if it's ext2). Right now,
> the assumption that syncing during suspend will cause data to hit
> something grub can read isn't a safe one.
I brought this issue up quite a few years ago at an OLS BOF. We pretty
much need a "s
Andrew Morton wrote:
On Sat, 9 Jun 2007 22:59:49 +0200 "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
Hmm, how's 2.6.22-rc4-mm2 doing on the Vaio?
People would have heard if it was busted ;)
Have seen occasional hangs in e100 resume-from-RAM, and occasional
all-black-and-dead symptoms after
Hi, thank you for your work. I was impressed.
BTW, how about adding following lines (both in Japanese and English) ?
==
This is translated "HOWTO" documentation. Original "HOWTO" is maintaind by
Greg Kroah-Hartman <[EMAIL PROTECTED]> and linux kernal mailing list.
And this one is maintained by T
Hi.
On Fri, 2007-06-01 at 21:54 -0400, Jeremy Maitin-Shepard wrote:
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> writes:
>
> >> But kernel threads also rely on userspace, due to e.g. fuse and usermode
> >> helpers.
>
> > Yes, I know that and I think these issues are solvable within the current
> >
On Sun, Jun 10, 2007 at 09:54:58PM +0100, Alan Cox wrote:
> > > GPLv2 probably forbids Tivoisation anyway. Which is good IMHO even if not
> >
> >
> > Now that is a bit waving in the air. GPLv2 forbids Tivoisation
> > theoretically but practically it didnt stop them doing it
On Sat, 2007-06-09 at 09:06 +0100, Jack Stone wrote:
> This patch adds a new macro to print to KERN_ERR initially for ncp but
> others may want to use it
Yes, the patch set takes away local control of debug printing that I may
need to turn on for the module without re-compiling the kernel.
>
> S
When building with memory hotplug enabled and cpu hotplug disabled, we
end up with the following section mismatch:
WARNING: mm/built-in.o(.text+0x4e58): Section mismatch: reference to
.init.text: (between 'free_area_init_node' and '__build_all_zonelists')
This happens as a result of:
->
Bartlomiej Zolnierkiewicz wrote:
Code intended to check DMA status was checking DMA command register.
Moreover firmware seems to "forget" to set DMA capable bit for the
slave device (at least in RAID mode but without ITE RAID volumes) so
check device ID for DMA capable bit when deciding whether
This makes DELTA and GET_TIME in drivers/input/gameport/gameport.c
similar to the ones in drivers/input/joystick/analog.c . Worked on
2.6.22-rc4-git2.
Signed-off-by: Miltiadis Margaronis <[EMAIL PROTECTED]>
--- a/drivers/input/gameport/gameport.c 2007-06-05 03:57:02.0 +0300
+++ b/dr
The following is CUMULATIVE to the previous push, but in the same linear
history. IOW, pulling 'linus-plus-plus' also gets you 'upstream-linus'.
But if you have already pulled 'upstream-linus', you will only receive
these two changesets.
Please pull from branch 'linus-plus-plus' of
master.kernel
Tejun Heo wrote:
After SRST, libata used to wait for nsect/lbal to be set to 1/1 for
the slave device. However, some ATAPI devices don't set nsect/lbal
after SRST and the wait itself isn't too useful as we're gonna wait
for !BSY right after that anyway.
Before reset-seq update, nsect/lbal wait
Hello, all.
Currently, there are several race conditions around dentry/inode
reclamation.
a. sysfs_dirent->s_dentry dereferencing in sysfs_readdir()
b. sysfs_dirent->s_dentry dereferencing in sysfs_drop_dentry()
c. sysfs_dirent->s_dentry clearing in sysfs_d_iput()
All aboves are done without s
On Mon, 11 Jun 2007 13:35:43 +0900
Paul Mundt <[EMAIL PROTECTED]> wrote:
> When building with memory hotplug enabled and cpu hotplug disabled, we
> end up with the following section mismatch:
>
> WARNING: mm/built-in.o(.text+0x4e58): Section mismatch: reference to
> .init.text: (between 'free_are
On 6/7/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Thu, 7 Jun 2007 17:01:08 +1000 Herbert Xu <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 07, 2007 at 08:54:50AM +0200, Jan Engelhardt wrote:
> >
> > /me points at Herbert
> > Andrew would not add options between the "menuconfig CRYPTO" and
> > the
From: Eric Sandeen <[EMAIL PROTECTED]>
Backport of
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc1/2.6.22-rc1-mm1/broken-out/gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
For regular files in sysfs, sysfs_readdir wants to traverse
sysfs_dirent->s_dentry->d_ino
Allowing attribute and symlink dentries to be reclaimed means
sd->s_dentry can change dynamically. However, updates to the field
are unsynchronized leading to race conditions. This patch adds
sysfs_lock and use it to synchronize updates to sd->s_dentry.
Due to the locking around ->d_iput, the ch
On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
> On Mon, 11 Jun 2007 13:35:43 +0900
> Paul Mundt <[EMAIL PROTECTED]> wrote:
>
> > When building with memory hotplug enabled and cpu hotplug disabled, we
> > end up with the following section mismatch:
> >
> > WARNING: mm/built-in
The condition check doesn't make much sense as it basically always
succeeds. This causes NULL dereferencing on certain cases. It seems
that parentheses are put in the wrong place. Fix it.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/inode.c |2 +-
1 file changed, 1 insertion(+
Mark,
On Sun, 2007-06-10 at 18:46 -0400, Mark Lord wrote:
> Do you know if there's anything specific in there that would fix
> the start-up race condition with HRTIMERS on my machine here
> (previously discussed, yet unresolved)?
>
> It still happens sporadically on boot-up -- maybe one in 10 boo
On Mon, 2007-06-11 at 09:26 +0900, Paul Mundt wrote:
>
> There are two paths here depending on hlt/nohlt setting, we need to have
> tick_nohz_stop_sched_tick() for the TIF_POLLING_NRFLAG case, too.
Do you really want to run through that in every loop iteration ? If you
have nohlt, then nohz is rat
On Mon, Jun 11, 2007 at 07:20:59AM +0200, Thomas Gleixner wrote:
> On Mon, 2007-06-11 at 09:26 +0900, Paul Mundt wrote:
> >
> > There are two paths here depending on hlt/nohlt setting, we need to have
> > tick_nohz_stop_sched_tick() for the TIF_POLLING_NRFLAG case, too.
>
> Do you really want to r
On Sun, Jun 10, 2007 at 07:52:28PM +0200, Sam Ravnborg wrote:
> On Sun, Jun 10, 2007 at 09:22:21AM -0700, Greg KH wrote:
> > > Since the common language of most kernel contributors is english I
> > > personally feel that we should stick to just that one language in the
> > > tree and then perhap
On Sun, Jun 10, 2007 at 07:56:52PM +0200, Matthias Schniedermeyer wrote:
> Greg KH wrote:
> > On Sun, Jun 10, 2007 at 02:24:51PM +0200, Jesper Juhl wrote:
> >> Since the common language of most kernel contributors is english I
> >> personally feel that we should stick to just that one language i
On Mon, Jun 11, 2007 at 11:55:57AM +0900, KAMEZAWA Hiroyuki wrote:
>
> Hi, thank you for your work. I was impressed.
>
> BTW, how about adding following lines (both in Japanese and English) ?
> ==
> This is translated "HOWTO" documentation. Original "HOWTO" is maintaind by
> Greg Kroah-Hartman <
Tarkan Erimer wrote:
> And maybe another questions should be : How long a copyright owner can
> hold the copyright, if died or lost for sometime ? if died, the
> copyright still should be valid or not ? If lost, what the law orders at
> this point for copyright holding ?
In most countries, copyrig
On Mon, 11 Jun 2007 14:01:07 +0900 Tejun Heo <[EMAIL PROTECTED]> wrote:
> Currently, there are several race conditions around dentry/inode
> reclamation.
>
> a. sysfs_dirent->s_dentry dereferencing in sysfs_readdir()
>
> b. sysfs_dirent->s_dentry dereferencing in sysfs_drop_dentry()
>
> c. sysf
Andrew Morton wrote:
>> This patchset contains three minimal backports of fixes in -mm. With
>> all patches in the patchset and sysfs-races.patch applied, kernel
>> survived ~20 hours of stress test without any problem.
>
> So these are being proposed for 2.6.22?
Yeap.
> I do wonder about Rafae
On Sun, 10 Jun 2007 22:01:34 -0700 "Dan Williams" <[EMAIL PROTECTED]> wrote:
> It would be very helpful to have a clear merge path for dmaengine
> changes and the async offload api.
Yes, this needs some attention.
I'd suggest that you prepare a standalone tree for Linus to pull and we aim at
ask
On Sun, 10 Jun 2007, Pavel Machek wrote:
extended out this can come close to giving each file it's own label. AA
essentially does this and calls the label the path and computes it at
runtime instead of storing it somewhere.
Yes, and in the process, AA stores compiled regular expressions in
ker
Greg KH wrote:
On Sun, Jun 10, 2007 at 05:21:53PM +0300, Tarkan Erimer wrote:
I hope we should upgrade to GPLv3 and Sun should "Dual License" the
OpenSolaris via GPLv3 (or at least,GPLv3 should be CDDL compatible.).
The OpenSolaris community has already stated that they do not want t
On Sun, 10 Jun 2007, Crispin Cowan wrote:
Casey Schaufler wrote:
--- [EMAIL PROTECTED] wrote:
Yes, and in the process, AA stores compiled regular expressions in
kernel. Ouch. I'll take "each file it's own label" over _that_ any time.
and if each file has it's own label you are going to need
On Sun, Jun 10, 2007 at 10:01:34PM -0700, Dan Williams wrote:
> Overall, I feel that async_tx is perhaps justifiably receiving the
> silent treatment because offload engines are not a mainstream
> occurrence. Currently only people with an Xscale IOP or a PPC 440spe
> [4] will notice that mainline
debian developer wrote:
On 6/10/07, Tarkan Erimer <[EMAIL PROTECTED]> wrote:
debian developer wrote:
> On 6/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> On Sun, 10 Jun 2007, Tarkan Erimer wrote:
>>
>> >> > And maybe another questions should be : How long a copyright
>> owner can
>> >>
Hi,
On 6/8/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
After few hours linux has crashed with this message:
BUG: at arch/i386/kernel/smp.c:546 smp_call_function()
Which kernel (exactly) was this, and does this occur
reproducibly? Also, could you please send the dmesg,
stack trace, etc for whe
On Sun, Jun 10, 2007 at 04:26:07PM +1000, Paul Mackerras wrote:
> If you don't think we should be bound by POSIX, then you are perfectly
> free to go off and write your own research kernel with whatever
> interface you want, and no programs available to run on it. :)
This isn't fair to research ke
Jeff Dike wrote:
On Thu, Jun 07, 2007 at 08:09:48AM +0300, Avi Kivity wrote:
Some extra logic is needed on i386 with >= 4GB. Current code will
wraparound since gfn_t is 32-bits long, but casting it to 64-bits is not
the answer since the processor will truncate it back to 32 bits (the
return
Satyam Sharma wrote:
On 6/7/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
Satyam Sharma wrote:
>
> Oh wait, the on_one_cpu() patch proposes on UP:
>
> +static inline int on_one_cpu(int cpu, void (*func)(void *info), void
> *info,
> + int retry, int wait)
> +{
>
> /* this needs a if (
On Thursday 07 June 2007, Bjorn Helgaas wrote:
> On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
> > I am beginning to doubt whether drier
> > works on my system at all (i.e. before PnP change); have to find time to
> > test.
>
> In 2.6.21, smsc-ircc2 at least found the device. So we
The command 'smartctl -a /dev/sdb' fails with 2.6.22-rc4 kernel. The
disk /dev/sdb is a SATA disk. The command does work still with a real SCSI
disk.
The computer has Athlon64 X2 and it is running x86_64 SMP kernel. The
chipset is Nvidia CK804 and the sata_nv driver is used.
The following outp
Hi!
> >So, AA developers, do you have such a document anywhere? I know there
> >are some old research papers, do they properly describe the current
> >model you are trying to implement here?
>
> Greg,
> to implement the AA approach useing SELinux you need to have a way that
> files that are r
Hi David,
David Schwartz wrote:
But; if the Linux kernel should Dual-Licensed (GPL V2 and GPL V3), it
will allow us the both worlds' fruits like code exchanging from other
Open Source Projects (OpenSolaris etc.) that is compatible with GPL V3
and not with GPL V2 and of course the opposite is app
Jan-Benedict Glaw wrote:
On Sat, 2007-06-09 15:57:55 +1000, Neil Brown <[EMAIL PROTECTED]> wrote:
On Saturday June 9, [EMAIL PROTECTED] wrote:
As we know the forthcoming GPL V3 will be not compatible with the GPL V2
and Linux Kernel is GPL V2 only.
So, another point is, which is previou
Hi Neil,
Neil Brown wrote:
On Saturday June 9, [EMAIL PROTECTED] wrote:
Hi,
As we know the forthcoming GPL V3 will be not compatible with the GPL V2
and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and others,
that if it is decided to upgrade t
On Jun 10 2007 11:37, Tarkan Erimer wrote:
>
> Thanks for the corrections ;-) The whole picture is more clear now for me :-)
> BTW,I found a really interesting blog entry about which code in Linux Kernel
> is
> using which version of GPL :
>
> http://6thsenseless.blogspot.com/2007/02/how-much-lin
On Sun, 10 Jun 2007, Pavel Machek wrote:
Hi!
So, AA developers, do you have such a document anywhere? I know there
are some old research papers, do they properly describe the current
model you are trying to implement here?
Greg,
to implement the AA approach useing SELinux you need to have
Linus Torvalds a écrit :
(And dammit, that _is_ a *real*issue*. No races necessary, no NR_OPEN
iterations, no even *halfway* suspect code. It's perfectly fine to do
close(0);
close(1);
close(2);
.. generate filenames, whatever ..
if (open(..) < 0 || open(
On 10/06/07 09:37, Tarkan Erimer wrote:
> BTW,I found a really interesting blog entry about which code in Linux
> Kernel is using which version of GPL :
>
> http://6thsenseless.blogspot.com/2007/02/how-much-linux-kernel-code-is-gpl-2.html
>
>
> The work done on a Linux 2.6.20. The result is quit
The following patch series contains:
- dyntick bugfixes for -mm (caused by the cpuidle changes in ACPI)
- updates and improvements to high resolution timer / dynticks
- high resolution timer / dynticks support for x86_64
The x86_64 support is based on an initial patch from Chris Wright. Thanks
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
include/linux/clockchips.h |4
1 file changed, 4 deletions(-)
Index: linux-2.6.22-rc4-mm/include/linux/clockchips.h
===
--- linux-2.6.22-rc4-mm.orig/include/linux/clock
From: Udo A. Steinberg <[EMAIL PROTECTED]>
The chipset doc for IHC4 tells us:
1.In general, software should not attempt any non-posted accesses during
arbiter disable except to the ICH4's power management registers. This implies
that interrupt handlers for any unmasked hardware interrupts and SMI
The cpuidle patches moved the tick nohz handling from irq_exit into
the inner idle loop. The change is correct as it covers non interrupt
based wakeups (e.g DMA) as well, but the move was only done for i386
and breaks ARM,SH and SPARC64.
Fix it up.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTE
clocksource_adjust() has a clock argument, which shadows the file
global clock variable. Fix this up.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: john stultz <[EMAIL PROTECTED]>
---
kernel/time/timekeeping.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
kernel/timer.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
Index: linux-2.6.22-rc4-mm/kernel/timer.c
===
--- linux-2.6.22-rc4-mm.orig/kerne
We need to make sure, that the clockevent devices are resumed, before
the tick is resumed. The current resume logic does not guarantee this.
Add CLOCK_EVT_MODE_RESUME and call the set mode functions of the clock
event devices before resuming the tick / oneshot functionality.
Fixup the existing us
The patch is necessary on one of my boxen, where programming the stop
sequence twice leads to PIT malfunction.
Sigh !
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
arch/i386/kernel/i8253.c |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
Index: linux-2.6.22-rc4-mm/arch
From: john stultz <[EMAIL PROTECTED]>
After discussing w/ Thomas over IRC, it seems the issue is the sched
tick fires on every cpu at the same time, causing extra lock contention.
This smaller change, adds an extra offset per cpu so the ticks don't
line up. This patch also drops the idle latency
When a device is replaced by a better rated device, then the broadcast
mode needs to be evaluated again. When the new device has no requirement
for broadcasting, then the broadcast bits for the CPU must be cleared.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
kernel/time/tick-broadcast
From: Ingo Molnar <[EMAIL PROTECTED]>
Add some more debug information to the hrtimer and clock events code.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
arch/i386/kernel/apic.c|3 +++
kernel/hrtimer.c |5 -
kerne
From: Ingo Molnar <[EMAIL PROTECTED]>
Speedup hrtimer_enqueue by evaluating the rbtree insertion result.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
kernel/hrtimer.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
Ind
Replace the pcspkr private PIT lock by the global PIT lock to
serialize the PIT access all over the place.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/time.c |2 ++
drivers/input/misc/pcspkr.c | 11 ---
include/asm-x86_64/i8253.h |6 ++
3 fi
From: Chris Wright <[EMAIL PROTECTED]>
I fixed this in x86_64. Looks like the kind of thing that will break
voyager on i386.
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c |2 +-
1 file changed, 1 insertion(+),
From: Chris Wright <[EMAIL PROTECTED]>
When making changes to x86_64 timers, I noticed that touching
hpet.h triggered an unreasonably large rebuild. Untangling
it from timex.h quiets the extra rebuild quite a bit.
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <
i386 and sparc64 have the identical code to update the cmos clock.
Move it into kernel/time/ntp.c as there are other architectures
coming along with the same requirements.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: Chris Wright <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc
Use the generic cmos update function in kernel/time/ntp.c
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: Chris Wright <[EMAIL PROTECTED]>
Cc: john stultz <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/Kconfig |4
arch/x86_64/kernel/time.c | 25 +++
setup_pit_timer is declared in asm-i386/timer.h. Move it to the
pit header file, so it can be used by x86_64 as well.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
include/asm-i386/i8253.h |2 ++
include/asm-i386/timer.h |1 -
2 files changed,
Remove unused code and variables and do some codingstyle / whitespace
cleanups while at it.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: john stultz <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/tsc.c | 41 +++--
1 f
From: Chris Wright <[EMAIL PROTECTED]>
Lost when merged with i386. Happy to drop, but I suspect Andi would
rather not break existing users (I noticed because it was part of my
testing). If dropped, Documentation needs updating.
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
Signed-off-by: Thom
From: Venki Pallipadi <[EMAIL PROTECTED]>
Disable irq balancing on IRQ0.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deleti
From: Chris Wright <[EMAIL PROTECTED]>
Everything is in place, enable the HIGHRES andf NO_HZ config options.
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_6
From: Chris Wright <[EMAIL PROTECTED]>
Add tick_nohz_{stop,restart}_sched_tick to idle
loop in prepartion for turning on dynticks. These
are just noops until NO_HZ is enabled in next patch.
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Cc: A
On Sunday June 10, [EMAIL PROTECTED] wrote:
> Hi Neil,
>
> Neil Brown wrote:
> > On Saturday June 9, [EMAIL PROTECTED] wrote:
> >
> >> Hi,
> >>
> >> As we know the forthcoming GPL V3 will be not compatible with the GPL V2
> >> and Linux Kernel is GPL V2 only.
> >> So, another point is, which i
Hi Thomas.
On Sun, 2007-06-10 at 09:44 +, Thomas Gleixner wrote:
> plain text document attachment (clockevents-fix-resume-logic.patch)
> We need to make sure, that the clockevent devices are resumed, before
> the tick is resumed. The current resume logic does not guarantee this.
>
> Add CLOCK
On Sun, 2007-06-10 at 19:43 +1000, Nigel Cunningham wrote:
> Hi Thomas.
>
> On Sun, 2007-06-10 at 09:44 +, Thomas Gleixner wrote:
> > plain text document attachment (clockevents-fix-resume-logic.patch)
> > We need to make sure, that the clockevent devices are resumed, before
> > the tick is re
[EMAIL PROTECTED] wrote:
On Sun, 10 Jun 2007, Tarkan Erimer wrote:
Date: Sun, 10 Jun 2007 11:43:28 +0300
From: Tarkan Erimer <[EMAIL PROTECTED]>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Jan-Benedict Glaw wrote:
On Sat, 2007-06-09 15:57:
On Sun, 10 Jun 2007, Tarkan Erimer wrote:
> And maybe another questions should be : How long a copyright owner can
> hold the copyright, if died or lost for sometime ? if died, the
> copyright still should be valid or not ? If lost, what the law orders at
> this point for copyright holding
Hi!
> > My other concerns with this patch are that it exports incorrect
> > information on spitz (which I had warned about and I will get bug
> > reports about) and that "description" is not really a suitable name for
> > a sysfs attribute, "function" might give a better idea of what it
> > repres
On Sunday, 10 June 2007 11:44, Thomas Gleixner wrote:
> We need to make sure, that the clockevent devices are resumed, before
> the tick is resumed. The current resume logic does not guarantee this.
>
> Add CLOCK_EVT_MODE_RESUME and call the set mode functions of the clock
> event devices before r
On Sun, 2007-06-10 at 12:19 +0200, Rafael J. Wysocki wrote:
> > -/*
> > - * Suspend/resume part
> > - */
> > -
> > -#ifdef CONFIG_PM
> > -
> > -static int hpet_suspend(struct sys_device *sys_device, pm_message_t state)
> > -{
> > - unsigned long cfg = hpet_readl(HPET_CFG);
> > -
> > - cfg &= ~(
On 6/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Sun, 10 Jun 2007, Tarkan Erimer wrote:
>> > And maybe another questions should be : How long a copyright owner can
>> > hold the copyright, if died or lost for sometime ? if died, the
>> > copyright still should be valid or not ? If
This patch replaces various array size calculations in drivers/isdn/hisax
done using sizeof with the ARRAY_SIZE macro.
Please CC me when you write comments, because I'm not subscribed
to the LKML.
Tested by compilation on an i386 box using "allyesconfig".
Diffed against Linus' git-tree.
Signed-o
Hi!
> > > > Any reason to not just replace ACPI_RSD_TABLE_SIZE with ARRAY_SIZE?
> >
> > Probably because ARRAY_SIZE doesn't exist in ACPICA, which is
> > where this code comes from...
> >
> > When we change syntax in ACPICA files in Linux to make it more "beautiful",
> > then it creates more wor
On Jun 10 2007 10:17, Simon Arlott wrote:
>On 10/06/07 09:37, Tarkan Erimer wrote:
>> BTW,I found a really interesting blog entry about which code in Linux
>> Kernel is using which version of GPL :
>>
>> http://6thsenseless.blogspot.com/2007/02/how-much-linux-kernel-code-is-gpl-2.html
>>
>> You'
On Sunday, 10 June 2007 12:30, Thomas Gleixner wrote:
> On Sun, 2007-06-10 at 12:19 +0200, Rafael J. Wysocki wrote:
> > > -/*
> > > - * Suspend/resume part
> > > - */
> > > -
> > > -#ifdef CONFIG_PM
> > > -
> > > -static int hpet_suspend(struct sys_device *sys_device, pm_message_t
> > > state)
> >
On Sat, 2007-06-09 at 13:12 -0700, Auke Kok wrote:
> Since the PCI bus class and revision are in the same dword, we
> can fill in both in the same read.
>
> Other non-x86 arches use different methods to fill in these values,
> make sure to adjust those too.
>
> Signed-off-by: Auke Kok <[EMAIL PRO
I am developing a stacking block driver and so far the driver was accepting
requests using the 'make_request' function (without a queue). When I switched to
using a request queue, I noticed that the driver received much more reuquests
in a
single call, which is very good for me.
The problem is th
Hi all,
I am posting Documentation/HOWTO which is translated into Japanese at
bottom of this email.
This document had been reviewed by JF project which has long history
to translate documents into Japanese. (not only kernel but also FAQs).
For JF, please see : http://www.linux.or.jp/JF/index.html
Satyam Sharma wrote:
> Hi,
ciao
> On 6/8/07, Marco Berizzi <[EMAIL PROTECTED]> wrote:
>> After few hours linux has crashed with this message:
>> BUG: at arch/i386/kernel/smp.c:546 smp_call_function()
>
> Which kernel (exactly) was this
2.6.21.3
> and does this occur
> reproducibly?
I don't
This is Japanese translation of "stable_api_nonsense.txt",
which is based on the same motivation of Tsugikazu Shibata.
-
Below lines are Japanese Translation of "stable_api_nonsense.txt"
---
+ dev->revision = get_int_prop(node, "revision-id", 0);
It's not clear to me in the spec if nodes are required to have the
"revision-id" property.
It is required for every PCI node.
I guess 0 is a safe default though.
As good as any -- that is, no default is save. 0 should
be "good
Luca wrote:
On 6/5/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
Luca Tettamanti wrote:
> Il Mon, Jun 04, 2007 at 11:51:10PM +0300, Avi Kivity ha scritto:
>
>>> While doing repeated tests with the installer I ran into another
>>> (unrelated) problem. Sometimes the guest kernel hangs at boot at:
>>>
On Jun 10 2007 21:03, IKEDA Munehiro wrote:
>
>This is Japanese translation of "stable_api_nonsense.txt",
>which is based on the same motivation of Tsugikazu Shibata.
Sweet! But could we have it in UTF-8?
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
On 10/06/07, Tsugikazu Shibata <[EMAIL PROTECTED]> wrote:
Hi all,
I am posting Documentation/HOWTO which is translated into Japanese at
bottom of this email.
Good job. I'm sure a lot of japanese people will appreciate that.
This document had been reviewed by JF project which has long history
On Jun 10 2007 14:24, Jesper Juhl wrote:
>
> If we start adding translated versions of documentation to the kernel
> source how should we organize the documents? Should each language get
> a sepperate directory in Documentation/ - like Documentation/JP/,
> Documentation/EN/, Documentation/DA/ etc?
On Sun, 10 Jun 2007, Neil Brown wrote:
> I presume the heirs of the dead people could change the license. And if
> they have no heir, then there is no-one to sue for breach of copyright,
> so I assume the copyright lapses.
In most of the law systems out there the copyright stays valid for 70
On Sunday 10 June 2007 08:45:41 Jiri Kosina wrote:
> On Sun, 10 Jun 2007, Neil Brown wrote:
> > I presume the heirs of the dead people could change the license. And if
> > they have no heir, then there is no-one to sue for breach of copyright,
> > so I assume the copyright lapses.
>
> In most of t
This is OK, thanks for changing.
On Sun, Jun 10, 2007 at 12:35:08PM +0200, Andi Drebes wrote:
> This patch replaces various array size calculations in drivers/isdn/hisax
> done using sizeof with the ARRAY_SIZE macro.
>
> Please CC me when you write comments, because I'm not subscribed
> to the LK
On Sun, 2007-06-10 15:11:22 +0200, Karsten Keil <[EMAIL PROTECTED]> wrote:
> > --- a/drivers/isdn/hisax/callc.c
> > +++ b/drivers/isdn/hisax/callc.c
> > @@ -834,7 +834,7 @@ static struct FsmNode fnlist[] __initdata =
> > };
> > /* *INDENT-ON* */
> >
> > -#define FNCOUNT (sizeof(fnlist)/sizeof(s
101 - 200 of 249 matches
Mail list logo
