Zachary Amsden wrote:
> No, it needs to be part of the general patch list first, which is
> still hand listed rather than just any op being patchable. Then it
> can be up to the backend.
Ah, right, yes. We need to add all (most? some?) of the pte operations
to that list too.
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:
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Zachary Amsden <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Zachary Amsden <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Zachary Amsden <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Prev by Date: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Next by Date: 2.6.20 mmc: problem with highspeed SD card
- Previous by thread: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Next by thread: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Index(es):
 |