From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Arve Hj?nnev?g <arve@android.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Brian Swetland <swetland@google.com>,
Daniel Walker <dwalker@codeaurora.org>,
Iliyan Malchev <malchev@google.com>
Subject: Re: [PATCH] staging/dream: add missing include files/fix compilation
Date: Thu, 14 Jan 2010 16:24:19 -0800 [thread overview]
Message-ID: <20100115002419.GA25643@kroah.com> (raw)
In-Reply-To: <20091225205917.GA25761@elf.ucw.cz>
On Fri, Dec 25, 2009 at 09:59:18PM +0100, Pavel Machek wrote:
> This adds missing include files, so it should now compile. ifdef
> guards were added to Kconfig, so it should not cause problems on
> non-arch-msm machines.
>
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
Odd, this doesn't apply to the linux-next tree, some of the files are
already there.
Care to refresh this?
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-15 0:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 20:59 [PATCH] staging/dream: add missing include files/fix compilation Pavel Machek
2010-01-15 0:24 ` Greg KH [this message]
2010-01-19 5:45 ` Pavel Machek
2010-01-19 15:14 ` Daniel Walker
2010-01-31 8:44 ` Pavel Machek
2010-01-31 9:28 ` Pavel Machek
2010-01-31 15:58 ` Daniel Walker
2010-02-25 19:30 ` Pavel Machek
2010-02-25 19:36 ` Daniel Walker
2010-02-25 19:41 ` Pavel Machek
2010-02-25 19:48 ` Daniel Walker
[not found] ` <20100226213107.GA29615@elf.ucw.cz>
[not found] ` <1267469856.29769.9.camel@c-dwalke-linux.qualcomm.com>
2010-03-01 21:10 ` Pavel Machek
2010-03-01 21:15 ` Daniel Walker
2010-03-01 21:41 ` Pavel Machek
2010-03-03 6:48 ` Pavel Machek
2010-01-31 13:31 ` Daniel Walker
2010-01-19 15:54 ` Greg KH
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=20100115002419.GA25643@kroah.com \
--to=greg@kroah.com \
--cc=arve@android.com \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malchev@google.com \
--cc=pavel@ucw.cz \
--cc=swetland@google.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