Chris Wright wrote: > It simply maps directly to the patch queue. We do go back and fold > things in and that should probably be done again, I agree. > Yeah, I've folded them all up now. Tracking xen-unstable is going to be tricker though. J - 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:
- [patch 31/32] xen: --- drivers/net/xen-netfront.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 31/32] xen: --- drivers/net/xen-netfront.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
- From: Herbert Xu <[email protected]>
- Re: [patch 31/32] xen: --- drivers/net/xen-netfront.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
- From: Chris Wright <[email protected]>
- [patch 31/32] xen: --- drivers/net/xen-netfront.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
- Prev by Date: Re: [patch 31/32] xen: --- drivers/net/xen-netfront.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
- Next by Date: Re: Natsemi DP83815 driver spaming
- Previous by thread: Re: [patch 31/32] xen: --- drivers/net/xen-netfront.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
- Next by thread: [patch 23/32] xen: Add the Xenbus sysfs and virtual device hotplug driver.
- Index(es):