From: Pavel Machek <pavel@ucw.cz>
To: Brian Swetland <swetland@google.com>
Cc: Greg KH <greg@kroah.com>,
malchev@google.com, kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: HTC Dream camera support for staging
Date: Thu, 9 Jul 2009 11:53:23 +0200 [thread overview]
Message-ID: <20090709095322.GB10937@elf.ucw.cz> (raw)
In-Reply-To: <a55d774e0907080247x23a2f134p1ecdb079c158df5@mail.gmail.com>
Hi!
> >> Can you resubmit it with the original author descriptions? It's not
> >> fair to them to have it shown up as coming from you.
> >
> > Yes, done... and thanks.
> >
> > Brian... I'd like to submit qdsp5 and smd code, too. Who should be
> > listed as their authors?
>
> smd is pretty much my fault at this point, though Arve hacks on the
> PM-related bits.
>
> The latest incarnation of the rpcrouter is me, with a lot of the
> original work by Iliyan, based heavily on the work Qualcomm did (thus
> their copyright on it as well as Google's).
>
> qdsp5 is Iliyan.
>
> Might be worth breaking these into at least three pieces (smd,
> rpcrouter, qdsp5)?
Sorry, I already submitted the patch. I just listed everyone I could
find in the sources in From: ; that included san@google but not
Arve. I hope that's not too bad.
> Are you highly opposed to having smd and rpcrouter under
> arch/arm/mach-msm? They're (for better or worse) pretty integral to
> the core operation of the platform (suspend/resume and a lot of other
> core SoC functions require coordination with the modem core).
I am not opposed to having the code under mach-msm/ ... it would be
actually preffered. But it is quite a lot of code, and I guess it
makes sense to clean it up in staging/ then move it to the proper
place.
Alternatively if you can create nice git series for rmk/-next; that
would work, too.
But I guess that staging/ stuff is quite easy to remove, and useful
for people that want to use the phones in the meantime :-).
> The qdsp5 stuff could exist elsewhere easily (though I'm not sure
> where the logical place is), and stuff on top of it like the v4l2
> camera stuff has obvious homes in the usual driver hierarchy.
Ack.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-09 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 11:43 Pavel Machek
2009-06-29 18:28 ` Guennadi Liakhovetski
2009-06-29 18:52 ` Greg KH
2009-07-02 20:08 ` Greg KH
2009-07-08 8:44 ` Pavel Machek
2009-07-08 9:47 ` Brian Swetland
2009-07-09 9:53 ` Pavel Machek [this message]
2009-07-09 15:00 ` Greg KH
[not found] ` <20090629121023.GD28046@google.com>
[not found] ` <20090630102457.GA25802@elf.ucw.cz>
[not found] ` <a55d774e0906300338l7743d566k5b463eed3efd1ea1@mail.gmail.com>
[not found] ` <20090709101315.GF10937@elf.ucw.cz>
[not found] ` <a55d774e0907090406u5e91b5c9r2303b098d0e44988@mail.gmail.com>
2009-07-13 20:27 ` Pavel Machek
2009-07-13 21:06 ` Pavel Machek
2009-07-13 22:05 ` Arve Hjønnevåg
2009-07-23 17:28 ` Pavel Machek
2009-07-08 8:40 Pavel Machek
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=20090709095322.GB10937@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=malchev@google.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
all inboxes | Powered by JetHome®