From: Daniel Walker <dwalker@fifo99.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: greg@kroah.com, swetland@google.com, malchev@google.com,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: HTC Dream: qdsp support for staging
Date: Sat, 11 Jul 2009 16:56:44 -0700 [thread overview]
Message-ID: <1247356604.5967.6.camel@desktop> (raw)
In-Reply-To: <20090711230509.GA4705@elf.ucw.cz>
On Sun, 2009-07-12 at 01:05 +0200, Pavel Machek wrote:
> On Fri 2009-07-10 10:25:57, Daniel Walker wrote:
> > On Fri, 2009-07-10 at 10:37 +0200, Pavel Machek wrote:
> > > From: Iliyan Malchev <ibm@android.com>
> > >
> > > QDSP code is neccessarry for communication with some hardware
> > > components on HTC Dream, including camera hardware. It also drives DSP
> > > coproccessor.
> > >
> > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> >
> > You don't want to break it up into multiple patches? I'll do it if you
> > don't want too ..
>
> I don't know how much sense it makes to split it further... yes, I
> could probably split it per file or something but...
>
> (Notice that this is going to be rewriten in staging, anyway, before
> merging into kernel proper...)
Your expecting a full re-write? From a quick look this stuff just looks
like it needs some TLC ..
Daniel
next prev parent reply other threads:[~2009-07-11 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 8:37 HTC Dream: qdsp support for staging Pavel Machek
2009-07-10 17:25 ` Daniel Walker
2009-07-11 23:05 ` Pavel Machek
2009-07-11 23:56 ` Daniel Walker [this message]
2009-07-12 10:28 ` Pavel Machek
2009-07-16 23:00 ` Greg KH
2009-07-17 1:01 ` Pavel Machek
2009-07-17 1:12 ` Greg KH
2009-07-17 11:30 ` Pavel Machek
2009-07-17 12:06 ` HTC Dream " Pavel Machek
2009-07-17 13:46 ` Greg KH
2009-07-17 13:57 ` Pavel Machek
2009-07-17 14:14 ` Greg KH
2009-07-18 10:41 ` Pavel Machek
2009-07-18 13:53 ` Daniel Walker
2009-07-18 15:04 ` 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=1247356604.5967.6.camel@desktop \
--to=dwalker@fifo99.com \
--cc=greg@kroah.com \
--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