From: "Brown, Len" <[EMAIL PROTECTED]>
Date: Sat, 3 Sep 2005 12:58:15 -0400
> CONFIG_AUDIT=y indeed did the trick.
>
> When will I be able to delete CONFIG_AUDIT from my kernel again?
It's a regression we accidently added to the netlink socket
family, we will fix it. But please use the workarou
From: Patrick McHardy <[EMAIL PROTECTED]>
Date: Mon, 08 Aug 2005 23:19:37 +0200
> David S. Miller wrote:
> > So we can increase MAX_LINKS to 256 and that's what I think I will do
> > for 2.6.14 unless there is a very serious objection. The tables sized
> >
mbers.
NETLINK_ARPD is unused, allocate it to the Open-iSCSI folks.
NETLINK_ROUTE6 and NETLINK_TAPBASE are no longer used, delete
them.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
diff --git a/include/linux/netlink.h b/include/linux/netlink.h
--- a/include/linux/netlink.h
+++
From: James Bottomley <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 15:23:20 -0500
> Actually, I saw this and increased MAX_LINKS as well.
That does absolutely nothing, you cannot create sockets
with protocol numbers larger than NPROTOS which like MAX_LINKS
has the value 32. And NPROTOS is somethin
From: Dmitry Yusupov <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 14:25:28 -0700
> It would be nice to set MAX_LINKS to 64 and close this issue for now,
James and Dmitry, increasing MAX_LINKS does't work, did you actually
try to open a netlink socket with a protocol number larger than 32?
It will
From: Christoph Hellwig <[EMAIL PROTECTED]>
Subject: Re: [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator
Date: Sat, 30 Jul 2005 20:38:03 +0200
> On Sat, Jul 30, 2005 at 11:36:22AM -0700, Alex Aizman wrote:
> > OK. Hopefully that'll remain.
>
> Please ask davem for a netlink num
From: James Bottomley <[EMAIL PROTECTED]>
Date: Sat, 30 Jul 2005 12:32:42 -0500
> FIB has taken your netlink number, so I changed it to 32
MAX_LINKS is 32, so there is no way this reassignment would
work.
You have to pick something in the range 0 --> 32, and as is
no surprise, there are no numbe
From: "Moore, Eric Dean" <[EMAIL PROTECTED]>
Date: Tue, 12 Jul 2005 14:50:19 -0600
> But Id rather have same files in our maintained driver,
> and whats in the kernel tree.
Just think what a mess we'd have on our hands if we let
everyone do that. Sorry, please don't put compat header
files into
Please don't add "linux-scsi-owner" to the CC: list like that.
That goes to the list administrator (currently me), not the
linux-scsi mailing list.
There seems to be a rather prominent influx of people sending
posts to the *-owner address lately, I wonder why as nothing has
materially changed in
On Sat, 02 Apr 2005 21:40:39 -0600
James Bottomley <[EMAIL PROTECTED]> wrote:
> After all, the driver must know the card is BE, so the routines that
> make use of the feature are easily coded into the card, so there's no
> real need to add it to the iomem cookie.
Yes, I don't believe it needs to
On Sun, 3 Apr 2005 02:37:57 +0100
Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> My thought on this is that we should encode the endianness of the
> registers in the ioremap cookie. Some architectures (sparc, I think?) can
> do this in their PTEs. The rest of us can do it in our ioread/writeN
> met
Matti Aarnio writes:
> I am contemplating to periodically turn off the ECN bit to
> let email out, but DaveM has veto there.
I veto, the whole point of moving to ECN was to make a statement and
get people to fix their kit.
We will remove these people, that's all.
Later,
Davi
12 matches
Mail list logo
