Aubrey Li <[email protected]> wrote: > Yes, it's reasonable for me, as long as your > host IP is 192.168.2.128 > and > target IP is 192.168.2.141 That is correct, yes:-) I expect it's an NFS packet as my board is using an NFS root at the moment. 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/
- References:
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: "Aubrey Li" <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: Robin Getz <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: "Wu, Bryan" <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: David Howells <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: Robin Getz <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: "Aubrey Li" <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- From: David Howells <[email protected]>
- Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- Prev by Date: Re: [PATCH] net/rxrpc: Convert to kthread API.
- Next by Date: [PATCH] use mutex instead of binary semaphore in FORE Systems 200E-series driver for ATM
- Previous by thread: Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- Next by thread: Re: [PATCH] CONFIG_PACKET_MMAP should depend on MMU
- Index(es):
 |