From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: mxsfb: Adapt to new videomode API
Date: Wed, 10 Apr 2013 11:27:59 +0300 [thread overview]
Message-ID: <5165228F.1020805@ti.com> (raw)
In-Reply-To: <1365516978-29888-1-git-send-email-fabio.estevam@freescale.com>
On 2013-04-09 17:16, Fabio Estevam wrote:
> commit 6cd2c7db4 (videomode: videomode_from_timing work) changed the name of
> the function from videomode_from_timing() to videomode_from_timings().
>
> commit 32ed6ef1 (videomode: create enum for videomode's display flags) changed
> the 'data_flags' field in videomode structure to 'flags'
>
> Adapt to these changes in order to fix the following errors:
>
> drivers/video/mxsfb.c:761:3: error: too many arguments to function 'videomode_from_timing'
> drivers/video/mxsfb.c:761:7: error: void value not ignored as it ought to be
> drivers/video/mxsfb.c:768:9: error: 'struct videomode' has no member named 'data_flags'
> drivers/video/mxsfb.c:770:9: error: 'struct videomode' has no member named 'data_flags'
>
> Also select VIDEOMODE_HELPER in Kconfig to avoid linker errors.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
The mxsfb.c driver in my tree does not contain such code. Where is this
patch meant to be applied?
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130410/3fb26f04/attachment.sig>
next prev parent reply other threads:[~2013-04-10 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:16 [PATCH] video: mxsfb: Adapt to new videomode API Fabio Estevam
2013-04-10 8:27 ` Tomi Valkeinen [this message]
2013-04-10 12:36 ` Fabio Estevam
2013-04-12 2:02 ` Shawn Guo
2013-04-12 6:25 ` Tomi Valkeinen
2013-04-12 6:30 ` Shawn Guo
2013-04-12 6:32 ` Tomi Valkeinen
2013-04-12 2:11 ` Shawn Guo
2013-04-12 2:24 ` Fabio Estevam
2013-04-12 2:55 ` Shawn Guo
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=5165228F.1020805@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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).