From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] cgroupsfs: new package
Date: Fri, 12 Feb 2016 17:14:34 +0100 [thread overview]
Message-ID: <56BE04EA.7070401@mind.be> (raw)
In-Reply-To: <20160212161722.48c9a703@free-electrons.com>
On 12-02-16 16:17, Thomas Petazzoni wrote:
> Hello,
>
> Thanks for this new iteration! See some comments below.
>
> On Fri, 12 Feb 2016 19:50:42 +0530, Niranjan Reddy wrote:
>> From: Niranjan <niranjan.reddy@rockwellcollins.com>
[snip]
>> + status)
>> + if mountpoint -q /sys/fs/cgroup; then
>> + # TODO decide whether to detect "partial mounted" status (ie, whether all available subsystems are mounted correctly)
>
> This comment needs to be wrapped. Or handled :)
Actually, we don't need status, only very old init scripts (or init scripts
delivered by the package) have that.
Regards,
Arnout
>
>> + echo "cgroupfs hierarchy is mounted"
>> + exit 0
>> + else
>> + echo "cgroupfs hierarchy is not mounted"
>> + exit 1
>> + fi
>> + ;;
>> +
>> + *)
>> + echo "Usage: $0 {start|stop|restart|status}"
>> + exit 1
>> + ;;
>> +esac
>
> Also, we often put the start(), stop() and status() code in functions,
> so that the indentation remains more reasonable. Again, see S50dropbear
> for a pretty good example.
>
[snip]
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-12 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 14:20 [Buildroot] [PATCH v2 1/1] cgroupsfs: new package Niranjan Reddy
2016-02-12 15:17 ` Thomas Petazzoni
2016-02-12 16:14 ` Arnout Vandecappelle [this message]
2016-02-16 6:08 ` Niranjan Reddy
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=56BE04EA.7070401@mind.be \
--to=arnout@mind.be \
--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