From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/busybox: update S10mdev
Date: Sat, 15 Jun 2019 19:34:14 +0300 [thread overview]
Message-ID: <20190615163414.GU9224@smile.fi.intel.com> (raw)
In-Reply-To: <mailman.4931.1560533212.86899.buildroot@busybox.net>
> On Wed, May 29, 2019 at 04:25:28PM +0200, Titouan Christophe wrote:
> > Avoid race conditions in mdev invocations
> > * use the uevent daemon if possible
> > * fallback to hotplug (as before) and initialize /dev/mdev.seq
> > * otherwise print an error message and do nothing else
> Thanks!
>
> Tested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>
> What are we going to do with this?
> As of today Buildroot can not be used with mdev in current state.
--
With Best Regards,
Andy Shevchenko
next parent reply other threads:[~2019-06-15 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4931.1560533212.86899.buildroot@busybox.net>
2019-06-15 16:34 ` Andy Shevchenko [this message]
2019-05-29 14:25 [Buildroot] [PATCH 1/1] package/busybox: update S10mdev Titouan Christophe
[not found] ` <20190614172647.GA32315@smile.fi.intel.com>
2019-06-16 20:15 ` Titouan Christophe
2019-06-18 19:33 ` Peter Korsgaard
2019-06-19 17:15 ` Titouan Christophe
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=20190615163414.GU9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.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.