Uttered Adam Litke <[EMAIL PROTECTED]>, spake thus:
> The line-wrapping in most of the include/asm/pgtable.h pte test/set
> macros looks horrible in my 80 column terminal. The following "test the
> waters" patch is how I would like to see them laid out. I realize that
> the braces don't adhere
Uttered Adam Litke [EMAIL PROTECTED], spake thus:
The line-wrapping in most of the include/asm/pgtable.h pte test/set
macros looks horrible in my 80 column terminal. The following test the
waters patch is how I would like to see them laid out. I realize that
the braces don't adhere to
Uttered Tomko <[EMAIL PROTECTED]>, spake thus:
> I would like to ask when a userprogram called in user space called
> execve("/bin/abc" will this system call finally copy the code of
> /bin/abc into kernel space before kernel runs it or just leave the code
> in the userspace and run
Uttered Tomko [EMAIL PROTECTED], spake thus:
I would like to ask when a userprogram called in user space called
execve(/bin/abc will this system call finally copy the code of
/bin/abc into kernel space before kernel runs it or just leave the code
in the userspace and run directly ?
Uttered Neal Gustafson <[EMAIL PROTECTED]>, spake thus:
> Blond Amateur Coed Spring Break Bed Sex Hardcore
> Blonde In Stockings Posing beaumont
Has this list not the simplest spam filter? It's difficult to see how any of
these original title terms could be from a legitimate posting.
Uttered Neal Gustafson [EMAIL PROTECTED], spake thus:
Blond Amateur Coed Spring Break Bed Sex Hardcore
Blonde In Stockings Posing beaumont
Has this list not the simplest spam filter? It's difficult to see how any of
these original title terms could be from a legitimate posting.
Uttered Andrew Morton <[EMAIL PROTECTED]>, spake thus:
> > if (uskb) {
> > netlink_unicast(dev->nls, uskb, 0, 0);
> > }
>
> Unneeded {}
Speaking strictly as a language lawyer, they are not needed.
However, for maintainability (and best practices) they are essential.
They
Uttered Andrew Morton [EMAIL PROTECTED], spake thus:
if (uskb) {
netlink_unicast(dev-nls, uskb, 0, 0);
}
Unneeded {}
Speaking strictly as a language lawyer, they are not needed.
However, for maintainability (and best practices) they are essential.
They make the
Uttered Geert Uytterhoeven <[EMAIL PROTECTED]>, spake thus:
> > There's probably a number of apps that skip the first two dirents, instead
> > of checking for the dot dirs.
>
> Yep, check `-noleaf' in find(1)
Then it is broken in several ways.
First, file systems are not required to
Uttered Geert Uytterhoeven [EMAIL PROTECTED], spake thus:
There's probably a number of apps that skip the first two dirents, instead
of checking for the dot dirs.
Yep, check `-noleaf' in find(1)
Then it is broken in several ways.
First, file systems are not required to implement ..
Uttered "Randy.Dunlap" <[EMAIL PROTECTED]>, spake thus:
> compile/build is wrong.
> a minimum 2.4 kernel build needs at least:
>
> gcc -c -D__KERNEL__ -DMODULE -O2 -nostdinc proc.c
Don't forget the kernel headers!
# gcc -c -D__KERNEL__ -DMODULE -O2 -I/usr/src/linux/include -nostdinc proc.c
Uttered Randy.Dunlap [EMAIL PROTECTED], spake thus:
compile/build is wrong.
a minimum 2.4 kernel build needs at least:
gcc -c -D__KERNEL__ -DMODULE -O2 -nostdinc proc.c
Don't forget the kernel headers!
# gcc -c -D__KERNEL__ -DMODULE -O2 -I/usr/src/linux/include -nostdinc proc.c
and, if
compiler warning
messages. If I don't get a useless message, I don't have to decide to ignore
it. Describing what's happening is OK; don't gush.
--
Tommy Reynolds |
Red Hat, Inc. (Embedded Development) | Join my presentation at:
307 Wynn Drive NW, Hun
get a useless message, I don't have to decide to ignore
it. Describing what's happening is OK; don't gush.
--
Tommy Reynolds |
Red Hat, Inc. (Embedded Development) | Join my presentation at:
307 Wynn Drive NW, Huntsville, AL 35805 USA | Red Hat TechWorld
14 matches
Mail list logo
