From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Miller <davem@davemloft.net>
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/fbde
Date: Mon, 29 Feb 2016 08:51:29 +0000 [thread overview]
Message-ID: <56D40691.6030002@ti.com> (raw)
In-Reply-To: <20160226.122112.1169840448330570848.davem@davemloft.net>
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
On 26/02/16 19:21, David Miller wrote:
> 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 disagree. Having drivers buildable as modules is always good, even if
the normal use case would be to have them as built-in.
> I plan to apply this patch series to my sparc tree as-is.
They are fbdev patches without any dependency to sparc afaics. So let's
apply them via fbdev tree.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Miller <davem@davemloft.net>
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: Mon, 29 Feb 2016 10:51:29 +0200 [thread overview]
Message-ID: <56D40691.6030002@ti.com> (raw)
In-Reply-To: <20160226.122112.1169840448330570848.davem@davemloft.net>
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
On 26/02/16 19:21, David Miller wrote:
> 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 disagree. Having drivers buildable as modules is always good, even if
the normal use case would be to have them as built-in.
> I plan to apply this patch series to my sparc tree as-is.
They are fbdev patches without any dependency to sparc afaics. So let's
apply them via fbdev tree.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-29 8:51 UTC|newest]
Thread overview: 18+ 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 ` 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 ` Paul Gortmaker
2016-02-22 3:13 ` [PATCH 2/3] drivers/video: make fbdev/sunxvr1000.c " Paul Gortmaker
2016-02-22 3:13 ` Paul Gortmaker
2016-02-22 3:13 ` [PATCH 3/3] drivers/video: make fbdev/sunxvr2500.c " Paul Gortmaker
2016-02-22 3:13 ` 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 10:58 ` Tomi Valkeinen
2016-02-26 13:58 ` Paul Gortmaker
2016-02-26 13:58 ` Paul Gortmaker
2016-02-29 8:44 ` Tomi Valkeinen
2016-02-29 8:44 ` Tomi Valkeinen
2016-02-26 17:21 ` [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc David Miller
2016-02-26 17:21 ` [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 David Miller
2016-02-29 8:51 ` Tomi Valkeinen [this message]
2016-02-29 8:51 ` 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=56D40691.6030002@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=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 \
/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.