From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91/defconfig: sama5: add CONFIG_FHANDLE
Date: Tue, 10 May 2016 14:46:52 +0200 [thread overview]
Message-ID: <5731D83C.3030308@denx.de> (raw)
In-Reply-To: <5731D71A.5080500@atmel.com>
On 05/10/2016 02:42 PM, Nicolas Ferre wrote:
> Le 10/05/2016 14:31, Marek Vasut a ?crit :
>> On 05/10/2016 10:03 AM, Nicolas Ferre wrote:
>>> CONFIG_FHANDLE is listed as a mandatory kernel option for systemd. So
>>> explicitly enable it to allow easy use of systemd userspace.
>>>
>>> Reported-by: Marek Vasut <marex@denx.de>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> ---
>>> Hi Marek,
>>
>> Hi!
>>
>>> It seems that on my side, CONFIG_FHANDLE is not selected automatically...
>>> So I add this patch: can you tell me your thoughts?
>>
>> Uh, weird, I tried this on next just now:
>>
>> linux-2.6$ git describe HEAD
>> next-20160510
>>
>> linux-2.6$ export ARCH=arm ; export CROSS_COMPILE=arm-linux-gnueabi-
>>
>> linux-2.6$ make sama5_defconfig ; grep FHANDLE .config
>> HOSTCC scripts/basic/fixdep
>> HOSTCC scripts/kconfig/conf.o
>> SHIPPED scripts/kconfig/zconf.tab.c
>> SHIPPED scripts/kconfig/zconf.lex.c
>> SHIPPED scripts/kconfig/zconf.hash.c
>> HOSTCC scripts/kconfig/zconf.tab.o
>> HOSTLD scripts/kconfig/conf
>> #
>> # configuration written to .config
>> #
>> CONFIG_FHANDLE=y
>
> Absolutely. The patch f76be61755c5 ("Make CONFIG_FHANDLE default y") has
> been added in v4.6-rc2... while I was doing my tests on at91-next that
> is based on v4.6-rc1 :-\
>
> Anyway. It's in now. Thanks,
Cool, thanks :)
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-05-10 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 20:31 [PATCH] ARM: at91: sama5: Update defconfig Marek Vasut
2016-05-06 14:30 ` Nicolas Ferre
2016-05-06 16:27 ` Marek Vasut
2016-05-10 8:03 ` [PATCH] ARM: at91/defconfig: sama5: add CONFIG_FHANDLE Nicolas Ferre
2016-05-10 12:31 ` Marek Vasut
2016-05-10 12:42 ` Nicolas Ferre
2016-05-10 12:46 ` Marek Vasut [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=5731D83C.3030308@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).