From: David Miller <davem@davemloft.net>
To: tomi.valkeinen@ti.com
Cc: paul.gortmaker@windriver.com, linux-kernel@vger.kernel.org,
plagnioj@jcrosoft.com, linux-fbdev@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code,Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code
Date: Fri, 26 Feb 2016 12:21:12 -0500 (EST) [thread overview]
Message-ID: <20160226.122112.1169840448330570848.davem@davemloft.net> (raw)
In-Reply-To: <56D02FB8.90803@ti.com>
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
Date: Fri, 26 Feb 2016 12:58:00 +0200
> While doing this, did you just go forward removing the module support,
> or did you check if it would be trivial to make the driver build as a
> module? I wouldn't be surprised if in some cases all that would need to
> be done is change the Kconfig's bool to tristate.
I think what he is doing is reasonable, and none of these sparc drivers
have any reason to be built modular. You need them to have any bootup
console whatsoever, so they have to be built in statically to be
usable at all.
I plan to apply this patch series to my sparc tree as-is.
next prev parent reply other threads:[~2016-02-26 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 3:13 [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code Paul Gortmaker
2016-02-22 3:13 ` [PATCH 1/3] drivers/video: make fbdev/sunxvr500.c explicitly non-modular Paul Gortmaker
2016-02-22 3:13 ` [PATCH 2/3] drivers/video: make fbdev/sunxvr1000.c " Paul Gortmaker
2016-02-22 3:13 ` [PATCH 3/3] drivers/video: make fbdev/sunxvr2500.c " Paul Gortmaker
2016-02-26 10:58 ` [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code Tomi Valkeinen
2016-02-26 13:58 ` Paul Gortmaker
2016-02-29 8:44 ` Tomi Valkeinen
2016-02-26 17:21 ` David Miller [this message]
2016-02-29 8:51 ` [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code,Re: " Tomi Valkeinen
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=20160226.122112.1169840448330570848.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=plagnioj@jcrosoft.com \
--cc=sparclinux@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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).