From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: fix mdev.conf
Date: Fri, 31 Mar 2017 09:00:59 +0200 [thread overview]
Message-ID: <87shlux74k.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170324075321.12384-1-joerg.krause@embedded.rocks> ("Jörg Krause"'s message of "Fri, 24 Mar 2017 08:53:21 +0100")
>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
> mdev does not set "/dev/snd" and "/dev/input" group and permission
> propery, because with commit c3cf1e30a3022453311a7e9fe11d94c7a381640e
> (May 2013!) the behavior of mdev has changed.
> The device name is now taken directly from the uevent file and does no
> longer match the old rule.
> Fix the rules for "/dev/snd" and "/dev/input" according to the example
> given in [1].
> [1] http://lists.busybox.net/pipermail/busybox/2015-February/082297.html
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-03-31 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 7:53 [Buildroot] [PATCH] busybox: fix mdev.conf Jörg Krause
2017-03-24 8:34 ` Arnout Vandecappelle
2017-03-25 13:54 ` Thomas Petazzoni
2017-03-31 7:00 ` Peter Korsgaard [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=87shlux74k.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox