public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <greg@kroah.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	arve@android.com, swetland@google.com,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch] Re: newer version of HTC Dream support
Date: Mon, 14 Sep 2009 23:46:19 +0200	[thread overview]
Message-ID: <20090914214619.GE10398@elf.ucw.cz> (raw)
In-Reply-To: <20090914212413.GA10043@kroah.com>

Hi!

> > > > Fix compilation of gpio_* input drivers on -next kernel. Adds needed
> > > > headers and removes unprotected wakelock/earlysuspend dependencies.
> > > >     
> > > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > > 
> > > Still doesn't build for me, but if it builds for you, that's great.
> > > (could be a tool chain problem on my side)
> > 
> > No, it does not look like toolchain problem :-(. I had parts disabled
> > in Kconfig. This should make it _compile_ (but not link); somehow
> > MSM_ADSP is neccessary for camera to link and I can't see how to
> > enable it.
> > 
> > Thanks for the patience.
> 
> Ugh, what patch should be applied in what order?  Care to resend them
> with the proper "x/y" and a valid Subject: line?

All of patches are valid, and they should apply if you just "sort by
date". I could dig them from my sent box...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-09-14 21:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  9:22 newer version of HTC Dream support Pavel Machek
2009-09-01 13:21 ` Pavel Machek
2009-09-04 16:03   ` Randy Dunlap
2009-09-11  7:16     ` Pavel Machek
2009-09-11 14:58       ` Randy Dunlap
2009-09-11 16:13         ` Pavel Machek
2009-09-11 16:21           ` Randy Dunlap
2009-09-11 21:27             ` [patch] " Pavel Machek
2009-09-11 22:34               ` Randy Dunlap
2009-09-13  8:37                 ` Pavel Machek
2009-09-13 20:54                   ` Randy Dunlap
2009-09-13 22:11                     ` Pavel Machek
2009-09-13 22:25                     ` Pavel Machek
2009-09-13 22:38                     ` Pavel Machek
2009-09-13 23:21                       ` Randy Dunlap
2009-09-14  7:06                         ` Pavel Machek
2009-09-14  7:11                         ` Pavel Machek
2009-09-14 19:56                           ` Randy Dunlap
2009-09-14 21:24                   ` Greg KH
2009-09-14 21:46                     ` Pavel Machek [this message]
2009-09-14 21:51                       ` Greg KH
2009-09-14 21:54                         ` Pavel Machek
2009-09-14 22:04                           ` Greg KH
2009-09-14 22:21                             ` Pavel Machek
2009-09-14 22:02                         ` Pavel Machek
     [not found]               ` <20090916174803.GA28689@kroah.com>
2009-09-26 11:44                 ` Staging: dream: fix build errorsg Pavel Machek
2009-09-26 18:48                   ` Daniel Walker

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=20090914214619.GE10398@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arve@android.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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