All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] rootfs.py: introduce USE_DEVFS check
Date: Wed, 02 Apr 2014 22:04:36 +0200	[thread overview]
Message-ID: <533C6D54.2040501@opendreambox.org> (raw)
In-Reply-To: <1396454510-5744-1-git-send-email-Matthieu.Crapet@ingenico.com>

Hello Matthieu,

On 02.04.2014 18:01, Matthieu Crapet wrote:
> Since commit a83144bac8d67704ff66f5dc0fc56f5b63979694 (2014-02-11), USE_DEVFS is not considered anymore.
> For compatibility, let's restore USE_DEVFS semantic.
> Also add USE_DEVFS to documentation.conf.
> 
> Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
> ---
>  meta/conf/documentation.conf | 1 +
>  meta/lib/oe/rootfs.py        | 3 ++-
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
> index 4d49a02..315e1b5 100644
> --- a/meta/conf/documentation.conf
> +++ b/meta/conf/documentation.conf
> @@ -436,6 +436,7 @@ UBOOT_MACHINE[doc] = "Specifies the value passed on the make command line when b
>  UBOOT_MAKE_TARGET[doc] = "Specifies the target called in the Makefile."
>  UBOOT_SUFFIX[doc] = "Points to the generated U-Boot extension."
>  UBOOT_TARGET[doc] = "Specifies the target used for building U-Boot."
> +USE_DEVFS[doc] = "When building images, specifies to populate or not ${sysconfdir}. This variable defaults to '1' (leave directory empty, surely because devtmpfs do the job). Set it to '0' to use makedevs (or consider using a custom file with IMAGE_DEVICE_TABLES)."

${sysconfdir} usually contains /etc, not /dev.

Regards,
Andreas


  reply	other threads:[~2014-04-02 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 15:15 [PATCH] rootfs.py: introduce USE_DEVFS check Matthieu Crapet
2014-04-02 15:52 ` Phil Blundell
2014-04-02 15:55   ` Matthieu CRAPET
2014-04-02 16:01 ` [PATCH v2] " Matthieu Crapet
2014-04-02 20:04   ` Andreas Oberritter [this message]
2014-04-03  7:05     ` [PATCH v3] " Matthieu Crapet

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=533C6D54.2040501@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.