Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH 4/4] Conditionally force on namespaces
Date: Fri, 5 Jun 2009 14:35:38 -0500	[thread overview]
Message-ID: <20090605193538.GA22848@us.ibm.com> (raw)
In-Reply-To: <20090605191530.04562DD1@kernel>

Quoting Dave Hansen (dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
> 
> This should work around the compile issues that Nathan
> pointed out yesterday.  It's too bad that 'select' is
> such a blunt object.  We could surely use a soft select
> or something.  But this hacks around it a bit.
> 
> Create a separate "*_NS_DEP" Kconfig option for the
> dependencies for each namespace.  Make the real config
> option and the c/r 'select' bot dependent on the new
> common one.
> 
> This should at least keep compile errors from being
> introduced.  Whether this is rude or not is a separate
> questions. :)

Yeah I'm not sure I'm a fan of this...

While I hate chasing down missing dependencies, maybe
CONFIG_CHECKPOINT should just depend on all the namespaces
instead of selecting them?

I'd assumed that was Nathan was really asking for, though
I could be wrong.

-serge

  reply	other threads:[~2009-06-05 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 19:15 [PATCH 1/4] Namespaces submenu Dave Hansen
2009-06-05 19:15 ` [PATCH 2/4] Move checkpoint closer to namespaces Dave Hansen
2009-06-05 19:15 ` [PATCH 3/4] kill 'Enable' in c/r config option Dave Hansen
2009-06-05 19:15 ` [PATCH 4/4] Conditionally force on namespaces Dave Hansen
2009-06-05 19:35   ` Serge E. Hallyn [this message]
     [not found]     ` <20090605193538.GA22848-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-06-05 21:21       ` Nathan Lynch
2009-06-08  6:21       ` Oren Laadan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090605193538.GA22848@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox