Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 0/5] udev is now provided by systemd or eudev
Date: Fri, 3 Jan 2014 17:11:06 +0100	[thread overview]
Message-ID: <20140103161104.GA3940@pc-eric> (raw)
In-Reply-To: <CAHXCMM+D0-FZKuj+_XXj5E3EfA+pud06t02LVE3ifQw+M_kGkA@mail.gmail.com>

Hi!

Thanks for the feedback!

On Fri, Jan 03, 2014 at 02:49:21PM +0100, Samuel Martin wrote:
>    The problems were:
>    - Some packages still use BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV after
>    applying the patchs:
>    A  $ git grep -l BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV
>    A  docs/manual/adding-packages-directory.txt
>    A  package/libmbim/Config.in
>    A  package/modem-manager/Config.in
>    A  package/network-manager/Config.in
modem-manager and libmbim are recent additions that fell off my radar...
I'll fix this and update my test configs.

>    - What does BR2_PACKAGE_UDEV_ALL_EXTRAS become?
This symbol has been removed after this discussion:
http://lists.busybox.net/pipermail/buildroot/2013-September/078503.html.

Best regards,
ELB

      reply	other threads:[~2014-01-03 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 12:44 [Buildroot] [PATCH v5 0/5] udev is now provided by systemd or eudev Eric Le Bihan
2014-01-03 12:44 ` [Buildroot] [PATCH v5 1/5] sysvinit: depend on SysV selected as init system Eric Le Bihan
2014-01-03 12:44 ` [Buildroot] [PATCH v5 2/5] eudev: new package Eric Le Bihan
2014-01-03 12:44 ` [Buildroot] [PATCH v5 3/5] udev: convert to virtual package Eric Le Bihan
2014-01-03 12:44 ` [Buildroot] [PATCH v5 4/5] systemd: bump to v207 Eric Le Bihan
2014-01-03 12:44 ` [Buildroot] [PATCH v5 5/5] manual: update /dev management section Eric Le Bihan
2014-01-03 13:49 ` [Buildroot] [PATCH v5 0/5] udev is now provided by systemd or eudev Samuel Martin
2014-01-03 16:11   ` Eric Le Bihan [this message]

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=20140103161104.GA3940@pc-eric \
    --to=eric.le.bihan.dev@free.fr \
    --cc=buildroot@busybox.net \
    /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