From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: balbi@ti.com
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Thomas Weber <weber@corscience.de>,
linux-omap@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Hans Verkuil <hverkuil@xs4all.nl>, Tejun Heo <tj@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] video: omap24xxcam: Fix compilation
Date: Tue, 15 Feb 2011 13:49:37 +0200 [thread overview]
Message-ID: <4D5A6851.20702@maxwell.research.nokia.com> (raw)
In-Reply-To: <20110215114710.GP2570@legolas.emea.dhcp.ti.com>
Felipe Balbi wrote:
> hi,
>
> On Tue, Feb 15, 2011 at 12:44:42PM +0100, Sylwester Nawrocki wrote:
>>> Are we using the same tree ? I don't see anything related to TASK_* on
>>
>> Please have a look at definition of macro wake_up. This where those
>> TASK_* flags are used.
>
> $ git grep -e TASK_ drivers/media/video/omap*.[ch]
> $
>
> ???
>
It's wake_up() on line 414.
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next prev parent reply other threads:[~2011-02-15 11:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 8:49 [PATCH resend] video: omap24xxcam: Fix compilation Thomas Weber
2011-02-07 16:15 ` Randy Dunlap
2011-02-15 11:28 ` Sakari Ailus
2011-02-15 11:37 ` Felipe Balbi
2011-02-15 11:44 ` Sylwester Nawrocki
2011-02-15 11:47 ` Felipe Balbi
2011-02-15 11:49 ` Sakari Ailus [this message]
2011-02-15 11:50 ` Thomas Weber
2011-02-15 11:53 ` Felipe Balbi
2011-02-15 12:17 ` Sakari Ailus
2011-02-19 11:35 ` David Cohen
2011-02-19 15:00 ` Felipe Balbi
2011-02-19 16:04 ` David Cohen
2011-02-21 7:36 ` Felipe Balbi
2011-02-21 12:09 ` David Cohen
2011-02-21 12:21 ` Felipe Balbi
2011-02-24 23:36 ` David Cohen
2011-02-25 6:59 ` Thomas Weber
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=4D5A6851.20702@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=balbi@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=s.nawrocki@samsung.com \
--cc=tj@kernel.org \
--cc=weber@corscience.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.