From: Khem Raj <raj.khem@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc
Date: Thu, 10 May 2018 12:26:39 -0700 [thread overview]
Message-ID: <4ab499de-5f57-520e-4951-91f15115435d@gmail.com> (raw)
In-Reply-To: <20180510191612.GB1954@jama>
On 5/10/18 12:16 PM, Martin Jansa wrote:
>> On second thought, this probably should be enabled using a config
>> fragment, since its not gonna link in another library it may not be
>> common case to justify for a default config.
> That's true, I've enabled CONFIG_FEATURE_MOUNT_NFS mostly to show how to
> reproduce the issue.
>
> If there isn't interest to enable this by default, I'm fine with keeping this
> locally (to enable it only with our defconfig changes which enable it).
>
I think keeping it as a nfsmount.cfg which then can be applied via a
bbappend could be a good option. May be adding a PACKAGECONFIG to
control the -I flag and libtirpc dependency would be nice too
next prev parent reply other threads:[~2018-05-10 19:26 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:26 [RFT] GCC 8.1 Khem Raj
2018-05-05 7:31 ` Zoran Stojsavljevic
2018-05-10 19:21 ` Khem Raj
2018-05-10 19:21 ` [yocto] " Khem Raj
2018-05-09 9:38 ` [OE-core] " Martin Jansa
2018-05-09 9:38 ` Martin Jansa
2018-05-09 9:38 ` Martin Jansa
2018-05-10 12:20 ` [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc Martin Jansa
2018-05-10 13:01 ` Burton, Ross
2018-05-10 18:21 ` Khem Raj
2018-05-10 18:24 ` Khem Raj
2018-05-10 19:16 ` Martin Jansa
2018-05-10 19:26 ` Khem Raj [this message]
2018-05-30 17:39 ` Andre McCurdy
2018-06-10 11:05 ` Martin Jansa
2018-05-10 18:50 ` [OE-core] [RFT] GCC 8.1 Khem Raj
2018-05-10 18:50 ` Khem Raj
2018-05-10 19:11 ` [OE-core] " Martin Jansa
2018-05-10 19:11 ` Martin Jansa
2018-05-10 19:27 ` [OE-core] " Andre McCurdy
2018-05-10 19:27 ` Andre McCurdy
2018-05-10 21:43 ` [OE-core] " Martin Jansa
2018-05-10 21:43 ` Martin Jansa
2018-05-10 22:07 ` [OE-core] " Martin Jansa
2018-05-10 22:07 ` Martin Jansa
2018-05-10 22:35 ` [OE-core] " Khem Raj
2018-05-10 22:35 ` Khem Raj
2018-05-10 22:38 ` [OE-core] " Andre McCurdy
2018-05-10 22:38 ` Andre McCurdy
2018-05-10 22:38 ` [OE-core] " Martin Jansa
2018-05-10 22:38 ` Martin Jansa
2018-05-10 22:38 ` Martin Jansa
2018-05-10 22:40 ` [OE-core] " Andre McCurdy
2018-05-10 22:40 ` Andre McCurdy
2018-05-10 22:50 ` [OE-core] " Martin Jansa
2018-05-10 22:50 ` Martin Jansa
2018-05-10 23:11 ` [OE-core] " Andre McCurdy
2018-05-10 23:11 ` Andre McCurdy
2018-05-10 23:32 ` [OE-core] " Martin Jansa
2018-05-10 23:32 ` Martin Jansa
2018-05-10 23:41 ` [OE-core] " Andre McCurdy
2018-05-10 23:41 ` Andre McCurdy
2018-05-11 0:55 ` [OE-core] " Khem Raj
2018-05-11 0:55 ` Khem Raj
2018-05-11 1:00 ` [OE-core] " Andre McCurdy
2018-05-11 1:00 ` Andre McCurdy
2018-05-11 1:06 ` [OE-core] " Khem Raj
2018-05-11 1:06 ` Khem Raj
2018-05-11 1:11 ` [OE-core] " Andre McCurdy
2018-05-11 1:11 ` Andre McCurdy
2018-05-11 1:16 ` [OE-core] " Khem Raj
2018-05-11 1:16 ` Khem Raj
2018-05-11 1:21 ` [OE-core] " Andre McCurdy
2018-05-11 1:21 ` Andre McCurdy
2018-05-17 10:46 ` [OE-core] " Martin Jansa
2018-05-17 10:46 ` Martin Jansa
2018-05-18 5:54 ` [OE-core] " Khem Raj
2018-05-18 5:54 ` Khem Raj
2018-05-24 15:08 ` [OE-core] " Martin Jansa
2018-05-24 15:08 ` Martin Jansa
2018-05-10 14:34 ` [OE-core] " Dan McGregor
2018-05-10 14:34 ` Dan McGregor
2018-05-10 18:53 ` [OE-core] " Khem Raj
2018-05-10 18:53 ` Khem Raj
2018-05-14 16:33 ` [OE-core] " Dan McGregor
2018-05-14 16:33 ` Dan McGregor
2018-05-14 17:09 ` [OE-core] " Martin Jansa
2018-05-14 17:09 ` Martin Jansa
2018-05-11 22:05 ` [OE-core] " Burton, Ross
2018-05-11 22:05 ` Burton, Ross
2018-05-12 6:10 ` [OE-core] " Khem Raj
2018-05-12 6:10 ` Khem Raj
2018-05-13 23:35 ` [OE-core] " Khem Raj
2018-05-13 23:35 ` Khem Raj
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=4ab499de-5f57-520e-4951-91f15115435d@gmail.com \
--to=raj.khem@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.