From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Marc Dietich <marvin24-Mmb7MZpHnFY@public.gmane.org>
Cc: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>,
Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
Erik Gilling <konkers-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ac100-+ipbUBPD95tH4x6Dk/4f9A@public.gmane.org
Subject: Re: nvec TODO
Date: Mon, 1 Aug 2011 12:46:50 +0100 [thread overview]
Message-ID: <20110801114650.GA19079@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201108011328.29440.marvin24-Mmb7MZpHnFY@public.gmane.org>
On Mon, Aug 01, 2011 at 01:28:28PM +0200, Marc Dietich wrote:
> Hi Russell, Greg,
>
> > Greg,
> >
> > A small patch to add something to this staging drivers todo list which
> > I just noticed. BTW, why isn't there any easy way to find a list of
> > addresses to copy against stuff in staging? I hope I have everyone...
>
> the Tegra/Nvidia/Google people are not involved in this driver development. The
> hw was used in the first generation Android devices only and became kind of
> obsolete (in kernels > .32 released by NV), but still there are a handfull older
> devices using it. That's why some community people (ml:
> ac100-oU9gvf+ajcQ97yFScArB1dHuzzzSOjJt@public.gmane.org, irc:#ac100 on freenode) try to port it to newer
> kernels.
That reinforces my point - there's no way to know who should be copied
with mails for stuff in staging.
> > The note is about something which should be easy enough to fix by people
> > who know the Tegra stuff (it probably involves changes outside of this
> > driver to fix.)
>
> I'll post some update to the driver soon (V2 of the patches I already submitted,
> http://driverdev.linuxdriverproject.org/pipermail/devel/2011-July/018751.html).
> In fact, the clock stuff should be done by the i2c-tegra driver and not in nvec
> itself. I hope I have time to prepare a corresponding patch for the next merge
> window (kernel 3.2). So the patch below is not needed anymore.
Good news.
Thanks.
next prev parent reply other threads:[~2011-08-01 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 10:45 nvec TODO Russell King - ARM Linux
[not found] ` <20110801104549.GG15578-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2011-08-01 11:28 ` Marc Dietich
[not found] ` <201108011328.29440.marvin24-Mmb7MZpHnFY@public.gmane.org>
2011-08-01 11:46 ` Russell King - ARM Linux [this message]
2011-08-01 11:48 ` Russell King - ARM Linux
[not found] ` <20110801114844.GB19079-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2011-08-01 12:27 ` Marc Dietich
2011-08-01 16:53 ` Greg KH
[not found] ` <20110801165316.GA2366-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2011-08-01 17:06 ` Russell King - ARM Linux
[not found] ` <20110801170616.GD19079-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2011-08-01 17:21 ` 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=20110801114650.GA19079@n2100.arm.linux.org.uk \
--to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
--cc=ac100-+ipbUBPD95tH4x6Dk/4f9A@public.gmane.org \
--cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=konkers-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marvin24-Mmb7MZpHnFY@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
/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