From: Bernd Kuhls <berndkuhls@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Discussing libudev, was: Re: [PATCH v6 09/32] mesa3d: dri2 does not need udev support
Date: Mon, 12 May 2014 22:59:40 +0200 [thread overview]
Message-ID: <sap74bxb7p.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20140512205324.GD3619@free.fr
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote in
news:20140512205324.GD3619 at free.fr:
> Now, this should be well integrated with the existing udev providers.
Hi,
reading the current code I am not sure what BR2_PACKAGE_HAS_UDEV means.
Currently only eudev and systemd select BR2_PACKAGE_HAS_UDEV, both are system
daemons while libudev being only a subset of them. I am not sure if libudev
should be a udev provider at all. My current patch includes
depends on !BR2_INIT_SYSTEMD
depends on !BR2_PACKAGE_EUDEV
Regards, Bernd
next prev parent reply other threads:[~2014-05-12 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 19:55 [Buildroot] Discussing libudev, was: Re: [PATCH v6 09/32] mesa3d: dri2 does not need udev support Bernd Kuhls
2014-05-12 20:53 ` Yann E. MORIN
2014-05-12 20:59 ` Bernd Kuhls [this message]
2014-05-12 21:02 ` Thomas Petazzoni
2014-05-12 21:12 ` Bernd Kuhls
2014-05-12 21:50 ` Thomas Petazzoni
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=sap74bxb7p.ln2@ID-313208.user.individual.net \
--to=berndkuhls@hotmail.com \
--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 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.