From: Vince Hsu <vinceh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] drm: merge nouveau_platform.ko into nouveau.ko
Date: Thu, 15 Jan 2015 15:00:10 +0800 [thread overview]
Message-ID: <54B7657A.2000609@nvidia.com> (raw)
In-Reply-To: <CAAVeFu+=-FQSGiL0Wqt2of1nYHd8qnXBw2jFUB6Z8+_p3kOr4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 01/15/2015 02:43 PM, Alexandre Courbot wrote:
> On Thu, Jan 15, 2015 at 3:39 PM, Ben Skeggs <skeggsb@gmail.com> wrote:
>> On Thu, Jan 15, 2015 at 4:29 PM, Alexandre Courbot <acourbot@nvidia.com> wrote:
>>> Having the two modules separated causes various unneeded complications,
>>> including having to export symbols accessed between the modules. Make
>>> things simpler by compiling platform device support into nouveau.ko.
>>> Platform device support remains optional and is only compiled on Tegra.
>>>
>>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>>> ---
>>> Vince, with this you won't have to export new functions for PM. I ended
>>> up writing it myself because I hit the same issue (nv_device() would now
>>> need to be exported on Ben's master branch).
>>>
>>> Be careful that when compiling against a kernel, CONFIG_NOUVEAU_PLATFORM_DRIVER
>>> now *must* be equal to 'y'. It is 'm' currently, so you will need to change it
>>> from tristate to bool in the kernel's Kconfig. For this reason it might be good
>>> to get this patch into -next quickly.
>> I've got a huge chunk of churn (finally finished the "rename to nvidia
>> names for stuff" thing) pending too which I want to get to Dave (ASAP,
>> separately from my other pending work) to avoid having to keep fixing
>> conflicts in the meantime :)
>>
>> So, if you guys both agree on the patch, I'll send it along early with those.
> That would be just perfect.
>
> Vince, do you have anything against this patch?
Of course not. I just tested it and it worked as good as expected.
Thanks for sending this.
Vince
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2015-01-15 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 6:29 [PATCH] drm: merge nouveau_platform.ko into nouveau.ko Alexandre Courbot
[not found] ` <1421303396-11867-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2015-01-15 6:39 ` Ben Skeggs
[not found] ` <CACAvsv6zHMizeA-r2qnngUaMXnorNfOXg6+998UWA4GzfFBOSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-15 6:43 ` [Nouveau] " Alexandre Courbot
[not found] ` <CAAVeFu+=-FQSGiL0Wqt2of1nYHd8qnXBw2jFUB6Z8+_p3kOr4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-15 7:00 ` Vince Hsu [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=54B7657A.2000609@nvidia.com \
--to=vinceh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.