public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] media: omapfb: relax compilation if COMPILE_TEST
Date: Sat, 7 Apr 2018 09:44:09 -0300	[thread overview]
Message-ID: <20180407094409.5fdc4672@vento.lan> (raw)
In-Reply-To: <3343566.MdR49rtcuZ@avalon>

Em Sat, 07 Apr 2018 14:46:56 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:

> Hi Mauro,
> 
> Thank you for the patch.
> 
> On Friday, 6 April 2018 18:33:20 EEST Mauro Carvalho Chehab wrote:
> > The dependency of DRM_OMAP = n can be relaxed for just
> > compilation test.
> > 
> > This allows building the omap3isp driver with allyesconfig
> > on ARM.  
> 
> omapfb has nothing to do with omap3isp. I assume you meant omap_vout.
> 
> There's a reason why both DRM_OMAP and FB_OMAP2 can't be compiled at the same 
> time, they export identical symbols. I believe you will end up with link 
> failures if you do so.

Ah, OK. I'll just drop this patch.

Thanks,
Mauro

  reply	other threads:[~2018-04-07 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 15:33 [PATCH 1/2] media: meye: relax dependencies if COMPILE_TEST Mauro Carvalho Chehab
2018-04-06 15:33 ` [PATCH 2/2] media: omapfb: relax compilation " Mauro Carvalho Chehab
2018-04-07 11:46   ` Laurent Pinchart
2018-04-07 12:44     ` Mauro Carvalho Chehab [this message]
2018-04-07  7:37 ` [PATCH 1/2] media: meye: relax dependencies " kbuild test robot

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=20180407094409.5fdc4672@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mchehab@infradead.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