Eric W. Biederman <[email protected]> wrote: > What is the ETA on your patches? That depends on Dave Miller now, I think. I'm assuming they need to go through the network GIT tree to get to Linus. Certainly Andrew Morton seems to think so. David - 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/
- Follow-Ups:
- Re: Getting the new RxRPC patches upstream
- From: David Howells <[email protected]>
- Re: Getting the new RxRPC patches upstream
- From: David Miller <[email protected]>
- Re: Getting the new RxRPC patches upstream
- From: David Howells <[email protected]>
- Re: Getting the new RxRPC patches upstream
- From: [email protected] (Eric W. Biederman)
- Re: Getting the new RxRPC patches upstream
- References:
- Re: [PATCH] net/rxrpc: Convert to kthread API.
- From: [email protected] (Eric W. Biederman)
- [PATCH] net/rxrpc: Convert to kthread API.
- From: "Eric W. Biederman" <[email protected]>
- Remaining straight forward kthread API conversions...
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH] net/rxrpc: Convert to kthread API.
- From: David Howells <[email protected]>
- Re: [PATCH] net/rxrpc: Convert to kthread API.
- Prev by Date: how to tell linux (on x86) to ignore 1M or memory
- Next by Date: Re: [PATCH RFD] alternative kobject release wait mechanism
- Previous by thread: Re: [PATCH] net/rxrpc: Convert to kthread API.
- Next by thread: Re: Getting the new RxRPC patches upstream
- Index(es):
 |