From: Tomi Valkeinen <tomi.valkeinen@iki.fi>
To: Rob Clark <robdclark@gmail.com>, Paul Bolle <pebolle@tiscali.nl>
Cc: David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"
Date: Fri, 28 Jun 2013 12:59:53 +0300 [thread overview]
Message-ID: <51CD5E99.5010802@iki.fi> (raw)
In-Reply-To: <CAF6AEGs_LS1ZFFj+C67dmRj4G122O1YSqTH_EpgtkLkQOKb2LQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]
On 15/06/13 15:20, Rob Clark wrote:
> On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle <pebolle@tiscali.nl> wrote:
>> On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote:
>>> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
>>> ---
>>> Untested. Perhaps the first test that people with access to the relevant
>>> hardware might do, is to test _before applying this patch_ with FB_OMAP2
>>> set. Perhaps this negative dependency isn't needed at all. Or is it
>>> obvious?
>>>
>>> drivers/gpu/drm/omapdrm/Kconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> This patch was sent exactly three months ago, shortly after v3.9-rc2 was
>> released. This obvious typo is still present in v3.10-rc5.
>>
>> I didn't received any feedback on this patch. Did anyone had a look at
>> it? Is it perhaps queued somewhere?
>
> oh, sorry, at the time I was in the middle of moving, and wasn't
> watching dri-devel so much.
>
> Yeah, this should probably either be merged, or we should just drop
> the negative dependency. (I guess in theory you could build both
> omapfb and omapdrm as modules and just load one.)
Hmm, fixing that creates a problem:
drivers/video/Kconfig:42:error: recursive dependency detected!
drivers/video/Kconfig:42: symbol FB is selected by DRM_KMS_HELPER
drivers/gpu/drm/Kconfig:29: symbol DRM_KMS_HELPER is selected by DRM_OMAP
drivers/gpu/drm/omapdrm/Kconfig:2: symbol DRM_OMAP depends on FB_OMAP2
drivers/video/omap2/omapfb/Kconfig:1: symbol FB_OMAP2 depends on FB
And it makes selecting omapfb not possible...
omapfb already has a !DRM_OMAP dependency. I think it's enough to have
that one there, and remove the !FB_OMAP dependency from omapdrm.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-06-28 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 19:48 [PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2" Paul Bolle
2013-06-13 10:31 ` Paul Bolle
2013-06-15 12:20 ` Rob Clark
2013-06-28 9:59 ` Tomi Valkeinen [this message]
2013-06-28 10:42 ` Dave Airlie
2013-06-15 10:09 ` Thierry Reding
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=51CD5E99.5010802@iki.fi \
--to=tomi.valkeinen@iki.fi \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=robdclark@gmail.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).