From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Anand Moon <linux.amoon@gmail.com>
Cc: k.kozlowski.k@gmail.com, Lukasz Majewski <l.majewski@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javier@osg.samsung.com>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
Kukjin Kim <kgene@kernel.org>
Subject: Re: [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
Date: Fri, 9 Oct 2015 19:47:15 +0900 [thread overview]
Message-ID: <56179B33.9030803@samsung.com> (raw)
In-Reply-To: <5276113.A7SSumyVrv@wuerfel>
W dniu 09.10.2015 o 19:28, Arnd Bergmann pisze:
> On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote:
>>
>>> I realize that building things as modules is a hassle, it is so for
>>> some things more than for others, so I keep asking the question
>>> to everyone to find out what a good balance is to make as much as
>>> possible modules without hurting too much.
>>
>> Fwiw, I don't find building modules overly cumbersome. Getting an
>> initramfs capable of moving on to an NFS root is mostly a one-time
>> thing (not unlike setting up the nfs root itself) and injecting modules
>> into it is relatively simple (doubly so if taking advantage of the
>> multiple cpio archive feature linux has).
>>
>> Interestingly, for me not building things as modules in multi_v7 tends
>> to cause more work as it hides a few categories of bugs that tend to
>> crop up once building distro kernels (e.g. missing module aliases,
>> missing module device table entries, implicitly relying on clocks being
>> active during probe as unused clocks only get turned of late in the
>> init sequence etc).
>>
>
> Ok, let's try to make all future network drivers modules in the
> multi_v7_defconfig then, and get people to use an initramfs
> if they need NFS root. If nobody complains too loudly for the
> next few releases, we can change the existing drivers to =m as well.
Personally I don't use NFS root and we don't have such configurations at
work. At least I am not aware of such. So from my point of view network
adapters as module is okay.
Anand,
Can you change it in multi_v7 patch to module?
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
Date: Fri, 9 Oct 2015 19:47:15 +0900 [thread overview]
Message-ID: <56179B33.9030803@samsung.com> (raw)
In-Reply-To: <5276113.A7SSumyVrv@wuerfel>
W dniu 09.10.2015 o 19:28, Arnd Bergmann pisze:
> On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote:
>>
>>> I realize that building things as modules is a hassle, it is so for
>>> some things more than for others, so I keep asking the question
>>> to everyone to find out what a good balance is to make as much as
>>> possible modules without hurting too much.
>>
>> Fwiw, I don't find building modules overly cumbersome. Getting an
>> initramfs capable of moving on to an NFS root is mostly a one-time
>> thing (not unlike setting up the nfs root itself) and injecting modules
>> into it is relatively simple (doubly so if taking advantage of the
>> multiple cpio archive feature linux has).
>>
>> Interestingly, for me not building things as modules in multi_v7 tends
>> to cause more work as it hides a few categories of bugs that tend to
>> crop up once building distro kernels (e.g. missing module aliases,
>> missing module device table entries, implicitly relying on clocks being
>> active during probe as unused clocks only get turned of late in the
>> init sequence etc).
>>
>
> Ok, let's try to make all future network drivers modules in the
> multi_v7_defconfig then, and get people to use an initramfs
> if they need NFS root. If nobody complains too loudly for the
> next few releases, we can change the existing drivers to =m as well.
Personally I don't use NFS root and we don't have such configurations at
work. At least I am not aware of such. So from my point of view network
adapters as module is okay.
Anand,
Can you change it in multi_v7 patch to module?
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-10-09 10:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 3:48 [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4 Anand Moon
2015-10-08 3:48 ` Anand Moon
2015-10-08 3:48 ` [PATCHv3 2/2] ARM: multi_v7_defconfig: " Anand Moon
2015-10-08 3:48 ` Anand Moon
2015-10-08 7:41 ` [PATCHv3 1/2] ARM: exynos_defconfig: " Arnd Bergmann
2015-10-08 7:41 ` Arnd Bergmann
2015-10-08 7:46 ` Krzysztof Kozlowski
2015-10-08 7:46 ` Krzysztof Kozlowski
2015-10-08 8:37 ` Arnd Bergmann
2015-10-08 8:37 ` Arnd Bergmann
2015-10-08 9:27 ` Sjoerd Simons
2015-10-08 9:27 ` Sjoerd Simons
2015-10-08 14:41 ` Arnd Bergmann
2015-10-08 14:41 ` Arnd Bergmann
2015-10-09 3:44 ` Anand Moon
2015-10-09 3:44 ` Anand Moon
2015-10-09 8:15 ` Arnd Bergmann
2015-10-09 8:15 ` Arnd Bergmann
2015-10-09 9:59 ` Sjoerd Simons
2015-10-09 9:59 ` Sjoerd Simons
2015-10-09 10:28 ` Arnd Bergmann
2015-10-09 10:28 ` Arnd Bergmann
2015-10-09 10:47 ` Krzysztof Kozlowski [this message]
2015-10-09 10:47 ` Krzysztof Kozlowski
2015-10-09 10:52 ` Anand Moon
2015-10-09 10:52 ` Anand Moon
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=56179B33.9030803@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=arnd@arndb.de \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=sjoerd.simons@collabora.co.uk \
/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.