From: Tony Lindgren <tony@atomide.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: omapfb: fix missing #includes
Date: Thu, 08 Feb 2018 15:38:58 +0000 [thread overview]
Message-ID: <20180208153858.GA4383@atomide.com> (raw)
In-Reply-To: <1518096294-14427-1-git-send-email-tomi.valkeinen@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [180208 13:25]:
> Something has changed with the include files and omapfb no longer
> compiles as it is not explicitly including linux/pinctrl/consumer.h and
> linux/seq_file.h.
>
> Add the missing #includes.
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> ---
>
> This is on top of today's Linus' master branch.
Can you guys please send this ASAP to Linus so we'll have
a v4.16-rc1 that actually compiles and boots?
Otherwise testing and bisecting various topic branches for v4.17
will suck :( Many of them will be based on v4.16-rc1.
Thanks and feel free to add:
Tested-by: Tony Lindgren <tony@atomide.com>
prev parent reply other threads:[~2018-02-08 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 13:24 [PATCH] video: omapfb: fix missing #includes Tomi Valkeinen
2018-02-08 15:38 ` Tony Lindgren [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=20180208153858.GA4383@atomide.com \
--to=tony@atomide.com \
--cc=linux-fbdev@vger.kernel.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).