From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Rework of shutdown policy in inittab
Date: Tue, 03 Jan 2012 11:22:24 +0100 [thread overview]
Message-ID: <4F02D6E0.7070909@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LUiEn75JpSsLK4O5_cj8qxgqRhEvNLjQ8sFAB2UjEYeEg@mail.gmail.com>
On 15/12/2011 09:44, Thomas De Schampheleire wrote:
> On Wed, Dec 14, 2011 at 5:46 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Le Wed, 7 Dec 2011 07:52:20 +0100,
>> Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
>>
>>> I think there are at least two solutions:
>>> 1. Keep the new behavior created with this patch, but make sure that
>>> the release notes clearly state this behavior change and update the
>>> documentation.
>>
>> I'd go for this one. All initscripts in Buildroot itself implement the
>> start/stop/restart logic, so author of scripts that haven't been
>> submitted upstream should have read this as a suggestion of following a
>> similar scheme.
>
> No problem for me. I also think this is the best alternative.
Then I guess we are all ok for it to be merged ? :)
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-01-03 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 12:25 [Buildroot] [PATCH] Rework of shutdown policy in inittab Maxime Ripard
2011-11-24 8:32 ` Maxime Ripard
2011-12-07 4:31 ` Kelvin Cheung
2011-12-07 6:52 ` Thomas De Schampheleire
2011-12-07 7:26 ` Kelvin Cheung
2011-12-07 9:50 ` Gustavo Zacarias
2011-12-07 13:08 ` Maxime Ripard
2011-12-08 9:33 ` Thomas De Schampheleire
2011-12-14 16:46 ` Thomas Petazzoni
2011-12-15 8:44 ` Thomas De Schampheleire
2012-01-03 10:22 ` Maxime Ripard [this message]
2012-01-03 10:48 ` Thomas De Schampheleire
-- strict thread matches above, loose matches on Subject: below --
2011-12-15 13:21 Sagaert Johan
2011-12-15 15:08 ` Thomas De Schampheleire
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=4F02D6E0.7070909@free-electrons.com \
--to=maxime.ripard@free-electrons.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