From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 2/2] systemd: select fsck wrapper from util-linux
Date: Wed, 12 Apr 2017 21:13:24 +0200 [thread overview]
Message-ID: <20170412211324.708186ef@free-electrons.com> (raw)
In-Reply-To: <1491997369-21394-3-git-send-email-casantos@datacom.ind.br>
Hello,
On Wed, 12 Apr 2017 08:42:49 -0300, Carlos Santos wrote:
> Select the fsck required by systemd provided by util-linux. This
> prevents ending up with fsck from busybox, which is incompatible
> with systemd.
>
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> [there were no v1, v2]
> Changes v3
> - Select e2fsprogs + e2fsck
> Changes v3->v4
> - Remove selection of e2fsprogs + e2fsck
> - Clean-up commit message
> Changes v4->v5
> - Screwed-up everything, reverting the chances made in v4
> Changes v5->v6
> - Restored changes made in v4.
> - Restore the patch changelog.
> Changes v6->v7
> - Removed spurious Change-Id from commit message.
> ---
> package/systemd/Config.in | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-12 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 11:42 [Buildroot] [PATCH v7 0/2] e2fsprogs: fix issues regarding merged /sbin and /usr/sbin Carlos Santos
2017-04-12 11:42 ` [Buildroot] [PATCH v7 1/2] e2fsprogs: refactor to fix conflicts with busybox and util-linux Carlos Santos
2017-04-12 11:42 ` [Buildroot] [PATCH v7 2/2] systemd: select fsck wrapper from util-linux Carlos Santos
2017-04-12 11:46 ` Arnout Vandecappelle
2017-04-12 19:13 ` 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=20170412211324.708186ef@free-electrons.com \
--to=thomas.petazzoni@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