From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: enable UEVENT_HELPER when mdev is used
Date: Sat, 1 Jun 2019 15:26:45 +0200 [thread overview]
Message-ID: <20190601152645.2ad18a4e@windsurf> (raw)
In-Reply-To: <38daf6b1-3749-66f4-93b9-7f1222c7da16@mind.be>
Hello,
On Wed, 29 May 2019 15:57:22 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> If you anyway have it, submit it, and we can discuss based on that.
Titouan has submitted his patch:
http://patchwork.ozlabs.org/patch/1107175/
The commit title is probably not the best, but other than that, the
idea looks good to me.
> It would be nice if you could also do a preparatory patch that converts the
> file to the "canonical init script format" (cfr. e.g.
> package/rsyslog/S01rsyslogd). mdev doesn't have arguments or a default, so that
> simplifies things a little.
Since the change to S10mdev from Titouan is kind of a fix, I would
actually not make the conversion to the "canonical format" a
requirement that should be done as a preparatory patch, but that's
admittedly a minor detail.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-01 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 13:07 [Buildroot] [PATCH] linux: enable UEVENT_HELPER when mdev is used Peter Korsgaard
2019-05-25 14:35 ` Andy Shevchenko
2019-05-25 15:24 ` Arnout Vandecappelle
2019-05-25 17:01 ` Andy Shevchenko
2019-05-25 19:56 ` Peter Korsgaard
2019-05-26 9:05 ` Arnout Vandecappelle
2019-06-03 14:56 ` Peter Korsgaard
2019-06-03 16:44 ` Titouan Christophe
2019-06-18 19:32 ` Peter Korsgaard
2019-07-29 10:00 ` Titouan Christophe
2019-07-31 6:20 ` Peter Korsgaard
2019-05-29 13:13 ` Titouan Christophe
2019-05-29 13:57 ` Arnout Vandecappelle
2019-06-01 13:26 ` Thomas Petazzoni [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=20190601152645.2ad18a4e@windsurf \
--to=thomas.petazzoni@bootlin.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