From: Jonathan Cameron <jic23@cam.ac.uk>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: soc-camera: status, roadmap
Date: Fri, 03 Jul 2009 18:59:50 +0000 [thread overview]
Message-ID: <4A4E5526.5040304@cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0906171458380.4218@axis700.grange>
Guennadi Liakhovetski wrote:
> On Wed, 10 Jun 2009, Guennadi Liakhovetski wrote:
>
>> 2. The above means, I'll have to maintain and update my patches for a
>> whole 2.6.31 development cycle. In this time I'll try to update and upload
>> them as a quilt patch series and announce it on the list a couple of
>> times.
>
> As promised, I just uploaded my current tree snapshot at
> http://download.open-technology.de/soc-camera/20090617/
> This is nothing remarkable, just my current patch-stack for those working
> with the soc-camera framework. It is still based on a linux-next snapshot
> of 07.05.2009 "history" branch. The exact commit on which the stack is
> based is, as usual, in 0000-base. This is still based off 2.6.30-rc4, and
> I expect to upgrade next time after 2.6.31-rc1.
>
Hi Guennadi,
I notice you've posted newer version of these patches on your website. 20090701/
I was wondering what tree these are based on?
I can't seem to track down the base commit.
Thanks,
Jonathan
next prev parent reply other threads:[~2009-07-03 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:45 soc-camera: status, roadmap Guennadi Liakhovetski
2009-06-10 20:09 ` Hans Verkuil
2009-06-10 21:49 ` Guennadi Liakhovetski
2009-06-10 22:00 ` Hans Verkuil
2009-06-11 0:31 ` Mauro Carvalho Chehab
2009-06-17 13:05 ` Guennadi Liakhovetski
2009-07-03 18:59 ` Jonathan Cameron [this message]
2009-07-03 19:20 ` Guennadi Liakhovetski
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=4A4E5526.5040304@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.