From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-media <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
FrankS <fschaefer.oss@googlemail.com>
Subject: Re: linux-next: Tree for Feb 29 (media: em28xx)
Date: Mon, 29 Feb 2016 13:23:05 -0800 [thread overview]
Message-ID: <56D4B6B9.8020200@infradead.org> (raw)
In-Reply-To: <20160229193034.0b663e03@canb.auug.org.au>
On 02/29/16 00:30, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160226:
>
on i386:
../drivers/media/usb/em28xx/em28xx-video.c: In function 'em28xx_v4l2_init':
../drivers/media/usb/em28xx/em28xx-video.c:2717:38: error: 'struct em28xx' has no member named 'media_dev'
ret = v4l2_mc_create_media_graph(dev->media_dev);
^
when CONFIG_MEDIA_CONTROLLER is not enabled.
--
~Randy
prev parent reply other threads:[~2016-02-29 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 8:30 linux-next: Tree for Feb 29 Stephen Rothwell
2016-02-29 21:23 ` Randy Dunlap [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=56D4B6B9.8020200@infradead.org \
--to=rdunlap@infradead.org \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.chehab@samsung.com \
--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).