Quoting Nathan Lynch (ntl@xxxxxxxxx): > Instead of trying to maintain a fruit salad of architecture names and > options in the dependency list, have architectures define > CHECKPOINT_SUPPORT in their respective Kconfigs when they have > implemented the arch-specific C/R hooks. > > Signed-off-by: Nathan Lynch <ntl@xxxxxxxxx> Yup, this is nicer, thanks. Acked-by: Serge Hallyn <serue@xxxxxxxxxx> > --- > checkpoint/Kconfig | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/checkpoint/Kconfig b/checkpoint/Kconfig > index e91e0fd..760c450 100644 > --- a/checkpoint/Kconfig > +++ b/checkpoint/Kconfig > @@ -1,6 +1,6 @@ > config CHECKPOINT > bool "Enable checkpoint/restart (EXPERIMENTAL)" > - depends on (X86_32 || (S390 && 64BIT)) && EXPERIMENTAL > + depends on CHECKPOINT_SUPPORT && EXPERIMENTAL > help > Application checkpoint/restart is the ability to save the > state of a running application so that it can later resume > -- > 1.6.0.6 > > _______________________________________________ > Containers mailing list > Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx > https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
