mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Trilok Soni" <soni.trilok@gmail.com>
To: "Hans Verkuil" <hverkuil@xs4all.nl>
Cc: v4l <video4linux-list@redhat.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"davinci-linux-open-source@linux.davincidsp.com" 
	<davinci-linux-open-source@linux.davincidsp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: v4l2_device/v4l2_subdev: please review
Date: Tue, 25 Nov 2008 12:57:29 +0530	[thread overview]
Message-ID: <5d5443650811242327gc204050lf232dfac48ae4f1@mail.gmail.com> (raw)
In-Reply-To: <200811250810.01767.hverkuil@xs4all.nl>

Hi Hans,

>
> I'm not going to spam the list with these quite big patches. Just go to
> http://linuxtv.org/hg/~hverkuil/v4l-dvb-ng/ and click on the 'raw' link
> after each change to see the patch. Most of these changes are just
> boring i2c driver conversions.

It is hard to review these patches from this link, as if you submit
the patch to ML then someone can just give inline comments to your
patch, otherwise reviewer has to copy that code which he/she wants to
comment while replying and not easy to track too. I don't know size
limit of this v4l2 ML, but linux-kernel ML can receive somewhat big
patches I believe.

>
> We are adding to the v4l core, but the changes do not affect existing
> v4l drivers let alone other subsystems. Although I should probably have
> added the omap list.

OMAP + soc-camera + v4l2-int-* community would be more interested to
see these patches as they need to change their sensor/controller
drivers to adapt your changes.

-- 
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni

  reply	other threads:[~2008-11-25  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200811242309.37489.hverkuil@xs4all.nl>
2008-11-25  6:51 ` Trilok Soni
2008-11-25  7:10   ` Hans Verkuil
2008-11-25  7:27     ` Trilok Soni [this message]
2008-11-25 17:48       ` v4l2_device/v4l2_subdev: please review (PATCH 1/3) Hans Verkuil
2008-11-28 23:34         ` Laurent Pinchart
2008-11-29 14:19           ` Hans Verkuil
2008-11-29 19:08             ` Guennadi Liakhovetski
2008-11-30 13:58               ` Hans Verkuil
2008-11-29 19:46             ` David Brownell
2008-11-29 19:53               ` Hans Verkuil
2008-11-30 21:02             ` Laurent Pinchart
2008-11-30 21:40               ` Hans Verkuil
2008-11-25 17:48       ` v4l2_device/v4l2_subdev: please review (PATCH 2/3) Hans Verkuil
2008-11-25 17:49       ` v4l2_device/v4l2_subdev: please review (PATCH 3/3) Hans Verkuil
2008-11-25  8:24 v4l2_device/v4l2_subdev: please review Hans Verkuil

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=5d5443650811242327gc204050lf232dfac48ae4f1@mail.gmail.com \
    --to=soni.trilok@gmail.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=video4linux-list@redhat.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®