From: Paul B. Henson <henson@acm.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mtd: add option to build mkfs.ubifs for target
Date: Tue, 30 Jul 2013 19:13:06 -0700 [thread overview]
Message-ID: <51F872B2.5080100@acm.org> (raw)
In-Reply-To: <20130729205101.17741846@skate>
On 7/29/2013 11:51 AM, Thomas Petazzoni wrote:
> Applied, thanks. I've made the changes suggested by Thomas De
> Schampheleire, as well as added the necessary 'depends on' statements
> for the requires toolchain features.
Cool, I appreciate you tuning it up for me.
It looks like you copied the dependencies from util-linux? I'm not that
familiar with kconfig, there's no concept of transitive dependencies,
such that if mkfs.ubifs selects util-linux, it will automatically
inherit its dependencies? If I'm understanding correctly, if at some
point util-linux changes dependencies, the mtd config for mkfs.ubifs
would also need to be updated explicitly to capture them?
Thanks much?
next prev parent reply other threads:[~2013-07-31 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 2:11 [Buildroot] [PATCH] mtd: add option to build mkfs.ubifs for target Paul B. Henson
2013-07-29 12:47 ` Thomas De Schampheleire
2013-07-29 18:20 ` Paul B. Henson
2013-07-29 18:51 ` Thomas Petazzoni
2013-07-31 2:13 ` Paul B. Henson [this message]
2013-07-31 6:48 ` Thomas Petazzoni
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=51F872B2.5080100@acm.org \
--to=henson@acm.org \
--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