On Wed, 2 Jan 2008, Herbert Xu wrote:
> Theodore Tso <[EMAIL PROTECTED]> wrote:
> > The question is whether the size of the Unix domain sockets support is
> > worth the complexity of yet another config option that we expose to
> > the user. For the embedded world, OK, maybe they want to save 14k
On Mon, 31 Dec 2007, David Miller wrote:
> From: Bodo Eggert <[EMAIL PROTECTED]>
> > The big question is: Is there any non-embedded system where you have
> > to aim for a small kernel image?
>
> One some platforms, due to bootloader restrictions or whatever,
> ther
On Mon, 31 Dec 2007, Al Viro wrote:
> On Mon, Dec 31, 2007 at 03:03:20PM +0100, Bodo Eggert wrote:
> > On Mon, 31 Dec 2007, David Miller wrote:
> > > From: Bodo Eggert <[EMAIL PROTECTED]>
> > > > As suggested by Adrian Bunk, UNIX domain sockets should alw
On Mon, 31 Dec 2007, Adrian Bunk wrote:
> On Mon, Dec 31, 2007 at 02:26:42PM +0100, Bodo Eggert wrote:
> > On Mon, 31 Dec 2007, Adrian Bunk wrote:
> > > On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote:
> > > > As suggested by Adrian Bunk, UNIX domain
On Mon, 31 Dec 2007, David Miller wrote:
> From: Bodo Eggert <[EMAIL PROTECTED]>
> > As suggested by Adrian Bunk, UNIX domain sockets should always be built in
> > on normal systems. This is especially true since udev needs these sockets
> > and fails to run if UNI
On Mon, 31 Dec 2007, Adrian Bunk wrote:
> On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote:
> > As suggested by Adrian Bunk, UNIX domain sockets should always be built in
> > on normal systems. This is especially true since udev needs these sockets
> > and f
In some of the Kconfig files, the options are not adequately decribed. I
collected a few of the bad descriptions I found:
---
Lowlevel video output switch controls (VIDEO_OUTPUT_CONTROL) [M/n/y/?] (NEW) ?
This framework adds support for low-level control of the video
output switch.
---
- What
As suggested by Adrian Bunk, UNIX domain sockets should always be built in
on normal systems. This is especially true since udev needs these sockets
and fails to run if UNIX=m.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
---
Last minute change: I decided against making it a bool b
Igor Sobrado <[EMAIL PROTECTED]> wrote:
> When code is multi-licensed it must be distributed under *all* these
> licensing terms concurrently.
No. E.g.:
If I don't agree to the GPL (or if I had violated it and therefore have lost
it's privileges), I MUST NOT redistribute it under the GPL because
Linas Vepstas <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 24, 2007 at 03:59:16PM +0200, Jan-Bernd Themann wrote:
>> 3) On modern systems the incoming packets are processed very fast. Especially
>> on SMP systems when we use multiple queues we process only a few packets
>> per napi poll cycle. So NAPI
Jerry Jiang <[EMAIL PROTECTED]> wrote:
> On Wed, 8 Aug 2007 21:18:25 -0700 (PDT)
>> On Wed, 8 Aug 2007, Chris Snook wrote:
>> > Some architectures currently do not declare the contents of an atomic_t to
>> > be
>> > volatile. This causes confusion since atomic_read() might not actually
>> > read
On Wed, 16 Aug 2006, Bill Nottingham wrote:
> Giacomo A. Catenazzi ([EMAIL PROTECTED]) said:
> > > Are you willing to work to add the special case code necessary to
> > > handle whitespace characters in the device name over all of the kernel
> > > code and also all of the userland tools too?
> >
Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> IMHO idiots who put space's in filenames should be ignored. As long as the
> bonding code doesn't throw a fatal error, it has every right to return
> "No such device" to the fool.
Maybe you should limit device names to eight uppercase characters and
Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> to some degree the in kernel balancer cannot really make the level of
> decisions that a userspace balancer can make, at least not without making all
> kernel developers vomit ;)
If you make the drivers set a flag if they know their interrupts should
Pavel Machek <[EMAIL PROTECTED]> wrote:
> +++ linux-mm/drivers/net/wireless/ipw2200.c
These are all uses of needs_reinit:
> +static int needs_reinit = 1;
> + needs_reinit = 1;
I asume there is something missing.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per S
Michael Buesch <[EMAIL PROTECTED]> wrote:
> How would the virtual interfaces look like? That is quite easy to answer.
> They are net_devices, as they transfer data.
> They should probaly _not_ be on top of the ethernet, as 80211 does not
> have very much in common with ethernet. Basically they sha
David S. Miller <[EMAIL PROTECTED]> wrote:
> The idea to mark, for example, IPSEC key management daemon's sockets
> as critical is flawed, because the key management daemon could hit a
> swap page over the iSCSI device. Don't even start with the idea to
> lock the IPSEC key management daemon into
17 matches
Mail list logo
