From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 28
Date: Fri, 28 Jun 2013 09:46:58 +0200 [thread overview]
Message-ID: <CA+icZUWtocVUaehLTF+oaXGyOX3_zASC_qMctZXzu59fFZGrcQ@mail.gmail.com> (raw)
In-Reply-To: <20130628173337.0ab94924c8c626093646caaf@canb.auug.org.au>
On Fri, Jun 28, 2013 at 9:33 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130627:
>
> This tree produces the following warning when built for many (all?)
> configs (it has been fixed in the drm tree):
>
> 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
>
Just FYI:
Patch pending in drm-next:
commit 2644ee9614be67abe155f1073bb9e1b737bbca53
"drm/omap: drop the !FB_OMAP2 dep"
- Sedat -
[1] http://cgit.freedesktop.org/~airlied/linux/patch/?id=2644ee9614be67abe155f1073bb9e1b737bbca53
next prev parent reply other threads:[~2013-06-28 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 7:33 linux-next: Tree for Jun 28 Stephen Rothwell
2013-06-28 7:46 ` Sedat Dilek [this message]
2013-06-28 16:49 ` linux-next: Tree for Jun 28 (net/nfc/nci) Randy Dunlap
2013-06-28 17:12 ` linux-next: Tree for Jun 28 (platform/x86/ce4100) Randy Dunlap
2013-06-28 17:24 ` linux-next: Tree for Jun 28 (net: gre) Randy Dunlap
2016-06-28 6:09 linux-next: Tree for Jun 28 Stephen Rothwell
2017-06-28 9:16 Stephen Rothwell
2018-06-28 6:20 Stephen Rothwell
2019-06-28 10:38 Stephen Rothwell
2021-06-28 10:57 Stephen Rothwell
2022-06-28 8:07 Stephen Rothwell
2023-06-28 4:27 Stephen Rothwell
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=CA+icZUWtocVUaehLTF+oaXGyOX3_zASC_qMctZXzu59fFZGrcQ@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).