Hi,
this is a small patch by Janusz Krzysztofik to ip_route_output_slow()
that allows VIP-less LVS linux director to generate packets originating
>From VIP if sysctl_ip_nonlocal_bind is set.
In a nutshell, the intention is for an LVS linux director to be able
to send ICMP unreachable responses t
From: Eric Dumazet <[EMAIL PROTECTED]>
Date: Sat, 10 Feb 2007 12:11:31 +0100
> [PATCH] : NET : restore multipath routing after rt_next changes
>
> I forgot to test build this part of the networking code... Sorry guys.
> This patch renames u.rt_next to u.dst.rt_next
>
> Signed-off-by: Eric Dumaze
Randy Dunlap wrote:
Jeff Garzik wrote:
Randy Dunlap wrote:
From: Randy Dunlap <[EMAIL PROTECTED]>
Convert function documentation in drivers/net/phy/ to kernel-doc
and add it to DocBook.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Documentation/DocBook/kernel-api.tmpl |6 +
driver
On Sat, Feb 10, 2007 at 12:53:51PM -0500, Pavel Roskin wrote:
> Quoting "John W. Linville" <[EMAIL PROTECTED]>:
>
> > > Very cool! Is it likely that d80211 and iwlwifi will be pushed into
> > > mainline in time for 2.6.21?
> >
> > Hmmm...I think we need to spend a cycle or so in -mm. 2.6.22 seem
On Saturday 10 February 2007 23:56, Pavel Roskin wrote:
> On Sat, 2007-02-10 at 22:11 +, Matthew Garrett wrote:
> > Ok, here's a patch. The stack of PCMCIA headers are needed to get the
> > pcmcia_device structure. Seems to work fine for PCI - I don't have any
> > PCMCIA devices. The SSB devi
On Sat, 2007-02-10 at 22:11 +, Matthew Garrett wrote:
> Ok, here's a patch. The stack of PCMCIA headers are needed to get the
> pcmcia_device structure. Seems to work fine for PCI - I don't have any
> PCMCIA devices. The SSB devices now appear underneath the PCI device
> rather than in the t
On Saturday 10 February 2007 23:11, Matthew Garrett wrote:
> On Sat, Feb 10, 2007 at 10:03:57PM +0100, Michael Buesch wrote:
> > On Saturday 10 February 2007 21:46, Matthew Garrett wrote:
> > > I'm testing with your bcm43xx git tree, which I'm guessing is the
> > > current ssb code. The only probl
On Sat, Feb 10, 2007 at 10:03:57PM +0100, Michael Buesch wrote:
> On Saturday 10 February 2007 21:46, Matthew Garrett wrote:
> > I'm testing with your bcm43xx git tree, which I'm guessing is the
> > current ssb code. The only problem I've found is that there doesn't seem
> > to be any sysfs relat
Jeff Garzik wrote:
Randy Dunlap wrote:
From: Randy Dunlap <[EMAIL PROTECTED]>
Convert function documentation in drivers/net/phy/ to kernel-doc
and add it to DocBook.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Documentation/DocBook/kernel-api.tmpl |6 +
drivers/net/phy/mdio_bus.c
On Saturday 10 February 2007 21:46, Matthew Garrett wrote:
> I'm testing with your bcm43xx git tree, which I'm guessing is the
> current ssb code. The only problem I've found is that there doesn't seem
> to be any sysfs relationship between the ssb bus and (in this case) the
> PCI device that it
I'm testing with your bcm43xx git tree, which I'm guessing is the
current ssb code. The only problem I've found is that there doesn't seem
to be any sysfs relationship between the ssb bus and (in this case) the
PCI device that it's associated with. Is this fixable? Right now it
appears as an en
On 07-02-10 10:51 Joe Perches wrote:
> On Sat, 2007-02-10 at 07:02 +0100, Michael Buesch wrote:
> > On Saturday 10 February 2007 02:27, Daniel Drake wrote:
> > > Robert P.J. Day's recent commit ("getting rid of all casts of
> > > k[cmz]alloc()
> > > calls") introduced a sparse warning for zd1211r
On Sat, 2007-02-10 at 07:02 +0100, Michael Buesch wrote:
> On Saturday 10 February 2007 02:27, Daniel Drake wrote:
> > Robert P.J. Day's recent commit ("getting rid of all casts of k[cmz]alloc()
> > calls") introduced a sparse warning for zd1211rw, related to our
> > type-checking
> > of addresses
On Saturday 10 February 2007 17:22, Theodore Tso wrote:
> On Fri, Feb 09, 2007 at 01:12:42PM -0800, James Ketrenos wrote:
> > Please hold all questions until I am done with this email. Thank you.
> >
> > We are pleased to announce the availability of a new driver for the
> > Intel PRO/Wireless 3
Quoting "John W. Linville" <[EMAIL PROTECTED]>:
> > Very cool! Is it likely that d80211 and iwlwifi will be pushed into
> > mainline in time for 2.6.21?
>
> Hmmm...I think we need to spend a cycle or so in -mm. 2.6.22 seems
> more likely for mainline.
I think we should take this as a goal. Las
On Friday, 9 February 2007 17:53, Michael Buesch wrote:
> On Friday 09 February 2007 17:18, Larry Finger wrote:
> > After a suspend/resume cycle, bcm43xx-softmac has lost its association with
> > the AP and requires manual intervention. This situation is fixed by making
> > one of softmac's interna
On Sat, Feb 10, 2007 at 11:22:54AM -0500, Theodore Tso wrote:
> On Fri, Feb 09, 2007 at 01:12:42PM -0800, James Ketrenos wrote:
> > Please hold all questions until I am done with this email. Thank you.
> >
> > We are pleased to announce the availability of a new driver for the
> > Intel PRO/Wire
On Fri, Feb 09, 2007 at 01:12:42PM -0800, James Ketrenos wrote:
> Please hold all questions until I am done with this email. Thank you.
>
> We are pleased to announce the availability of a new driver for the
> Intel PRO/Wireless 3945ABG Network Connection adapter. This new driver
> uses the ne
Hi,
Jeff Garzik, le Fri 09 Feb 2007 16:15:26 -0500, a écrit :
> Levitsky Maxim wrote:
> >Before some time I decided to fix suspend/resume on my Davicom
> >network card. During development I also fixed couple of bugs and
> >added support for link detection and WOL Note : 2.6.20 already has
> >supp
Hi,
Here goes an updated patch of the Marvell Libertas 8388 802.11 USB
driver, addressing pretty much all comments from Arnd (the remaining
ones are listed in TODO entry below).
Diff can be found at
http://dev.laptop.org/~marcelo/libertas-8388-10022007.patch
Please review.
TODO:
- In places wh
On Saturday 10 February 2007 14:23, Hesse, Christian wrote:
> On Friday 09 February 2007 22:12, James Ketrenos wrote:
> > We are pleased to announce the availability of a new driver for the
> > Intel PRO/Wireless 3945ABG Network Connection adapter.
>
> Wow, great news on this rainy saturday! ;-)
>
On Sat, Jan 27, 2007 at 02:53:07AM +0100, Arnd Bergmann wrote:
> > +/** Command Processing States and Options */
> > +#define HostCmd_STATE_IDLE0x
> > +#define HostCmd_STATE_IN_USE_BY_HOST 0x0001
> > +#define HostCmd_STATE_IN_USE_BY_MINIPORT 0x0002
> > +#define
On Friday 09 February 2007 22:12, James Ketrenos wrote:
> We are pleased to announce the availability of a new driver for the
> Intel PRO/Wireless 3945ABG Network Connection adapter.
Wow, great news on this rainy saturday! ;-)
The driver works perfectly, I'm writing this mail via wireless link. H
On Sat, Feb 10, 2007 at 06:55:50AM +0100, Michael Buesch wrote:
> We don't know.
>
> It's likely that old cards still work with v4 firmware, but we don't know and
> it has to be tested.
>
> Care to do so?
I'll check the revision of my 4306, but I think it's probably too new to
be useful, unfor
Andrew Morton a écrit :
net/ipv4/multipath_rr.c: In function 'rr_select_route':
net/ipv4/multipath_rr.c:60: error: 'union ' has no member named
'rt_next'
net/ipv4/multipath_rr.c:60: warning: type defaults to 'int' in declaration of
'_p1'
net/ipv4/multipath_rr.c:60: error: 'union ' has n
David Miller a écrit :
From: Eric Dumazet <[EMAIL PROTECTED]>
Date: Thu, 08 Feb 2007 22:32:10 +0100
I prepared the following five patches :
[PATCH 1/5] : Introduce union in struct dst_entry, to prepare patches 2,3,4
[PATCH 2/5] : Convert ipv4 route to use the new dst_entry 'next' pointer
[PATC
26 matches
Mail list logo