Christoph Hellwig wrote:
On Wed, Oct 03, 2007 at 10:40:25PM -0400, Casey Dahlin wrote:
From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
From: Casey Dahlin <[EMAIL PROTECTED]>
Date: Wed, 3 Oct 2007 22:01:49 -0400
Subject: [PATCH] Code style fix for open_exe
Christoph Hellwig wrote:
On Wed, Oct 03, 2007 at 10:40:25PM -0400, Casey Dahlin wrote:
From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
From: Casey Dahlin [EMAIL PROTECTED]
Date: Wed, 3 Oct 2007 22:01:49 -0400
Subject: [PATCH] Code style fix for open_exec
Fix
Ingo Molnar wrote:
* Jarek Poplawski <[EMAIL PROTECTED]> wrote:
[...] (Btw, in -rc8-mm2 I see new sched_slice() function which seems
to return... time.)
wrong again. That is a function, not a variable to be cleared.
It still gives us a target time, so could we not simply have
From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
From: Casey Dahlin <[EMAIL PROTECTED]>
Date: Wed, 3 Oct 2007 22:01:49 -0400
Subject: [PATCH] Code style fix for open_exec
Fix a horribly mangled 5 level indent and severe abuse of goto in the
open_exec
function.
Sign
From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
From: Casey Dahlin [EMAIL PROTECTED]
Date: Wed, 3 Oct 2007 22:01:49 -0400
Subject: [PATCH] Code style fix for open_exec
Fix a horribly mangled 5 level indent and severe abuse of goto in the
open_exec
function.
Signed-off
Ingo Molnar wrote:
* Jarek Poplawski [EMAIL PROTECTED] wrote:
[...] (Btw, in -rc8-mm2 I see new sched_slice() function which seems
to return... time.)
wrong again. That is a function, not a variable to be cleared.
It still gives us a target time, so could we not simply have
: Tue, 11 Sep 2007 18:05:15 -0400
From: Casey Dahlin <[EMAIL PROTECTED]>
To: Linux Kernel
I have an Asus Striker Extreme motherboard with two built in MCP55 GigE
interfaces. When I build with the original Fedora 7 release kernel (
ftp://ftp.belnet.be/linux/fedora/linux/re
: Tue, 11 Sep 2007 18:05:15 -0400
From: Casey Dahlin [EMAIL PROTECTED]
To: Linux Kernel linux-kernel@vger.kernel.org
I have an Asus Striker Extreme motherboard with two built in MCP55 GigE
interfaces. When I build with the original Fedora 7 release kernel (
ftp://ftp.belnet.be
Casey Dahlin wrote:
I have an Asus Striker Extreme motherboard with two built in MCP55
GigE interfaces. When I build with the original Fedora 7 release
kernel (
ftp://ftp.belnet.be/linux/fedora/linux/releases/7/Fedora/i386/os/Fedora/kernel-2.6.21-1.3194.fc7.i686.rpm
) everything works fine
Casey Dahlin wrote:
I have an Asus Striker Extreme motherboard with two built in MCP55
GigE interfaces. When I build with the original Fedora 7 release
kernel (
ftp://ftp.belnet.be/linux/fedora/linux/releases/7/Fedora/i386/os/Fedora/kernel-2.6.21-1.3194.fc7.i686.rpm
) everything works fine
, but at this point I'm at a complete loss.
-Casey Dahlin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
, but at this point I'm at a complete loss.
-Casey Dahlin
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Sorry to have left this dormant for so long.
Running eject in either of the ways suggested still leaves the light on
my particular key turned on.
Stefan Richter wrote:
Guennadi Liakhovetski wrote:
I might imagine how windows turns the LED off on
unmount. Try "eject /dev/sdX", where sdX
Sorry to have left this dormant for so long.
Running eject in either of the ways suggested still leaves the light on
my particular key turned on.
Stefan Richter wrote:
Guennadi Liakhovetski wrote:
I might imagine how windows turns the LED off on
unmount. Try eject /dev/sdX, where sdX is
Suppose you saw some other variant of *nix that had some code you wanted
to use, but there was a gaping security hole in it. Wouldn't you patch
it before you incorporated it? and would it be your fault if this fix
made the code not work with the original?
We took the code and fixed a gaping
Suppose you saw some other variant of *nix that had some code you wanted
to use, but there was a gaping security hole in it. Wouldn't you patch
it before you incorporated it? and would it be your fault if this fix
made the code not work with the original?
We took the code and fixed a gaping
, the light is simply on whenever the key is plugged in.
Should linux toggle the light depending on mount state? Is it as trivial
as it seems or does this reflect some larger issue?
-Casey Dahlin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
, the light is simply on whenever the key is plugged in.
Should linux toggle the light depending on mount state? Is it as trivial
as it seems or does this reflect some larger issue?
-Casey Dahlin
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Michael Tharp wrote:
Marc Perkel wrote:
The important point that you are missing here is that
the Linux world is willing to live with an rm command
that is broken and the Windows and DOS world isn't.
This isn't about the rm command it's about programming
standards. It's about that the Linux
Michael Tharp wrote:
Marc Perkel wrote:
The important point that you are missing here is that
the Linux world is willing to live with an rm command
that is broken and the Windows and DOS world isn't.
This isn't about the rm command it's about programming
standards. It's about that the Linux
20 matches
Mail list logo
