linux-kernel - Re: HTC Dream camera support for staging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090709095322.GB10937@elf.ucw.cz>
Date:	Thu, 9 Jul 2009 11:53:23 +0200
From:	Pavel Machek <pavel@....cz>
To:	Brian Swetland <swetland@...gle.com>
Cc:	Greg KH <greg@...ah.com>, malchev@...gle.com,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: HTC Dream camera support for staging

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@...gle 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/