The patch number 10495 was added via Mauro Carvalho Chehab <mche...@redhat.com>
to http://linuxtv.org/hg/v4l-dvb master development tree.
Kernel patches in this development tree may be modified to be backward
compatible with older kernels. Compatibility modifications will be
removed before inclusion into the mainstream Kernel
If anyone has any objections, please let us know by sending a message to:
Linux Media Mailing List <linux-me...@vger.kernel.org>
------
From: Mauro Carvalho Chehab <mche...@redhat.com>
merge: http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-spec
Priority: normal
Signed-off-by: Mauro Carvalho Chehab <mche...@redhat.com>
---
.hgignore | 6 ++++
README.patches | 61 ++++++++++++++++++++++++++-----------------------
2 files changed, 39 insertions(+), 28 deletions(-)
diff -r e3896c8892a5 -r d76f0c9b75fd .hgignore
--- a/.hgignore Tue Feb 10 01:31:47 2009 +0100
+++ b/.hgignore Tue Feb 10 04:47:31 2009 -0200
@@ -63,3 +63,9 @@ v4l2-spec/v4l2$
v4l2-spec/v4l2$
v4l2-spec/v4l2.pdf$
v4l2-spec/videodev2.h.sgml$
+v4l/firmware/cpia2/stv0672_vp4.bin
+v4l/firmware/dabusb/bitstream.bin
+v4l/firmware/dabusb/firmware.fw
+v4l/firmware/ihex2fw
+v4l/firmware/ttusb-budget/dspbootcode.bin
+v4l/firmware/vicam/firmware.fw
diff -r e3896c8892a5 -r d76f0c9b75fd README.patches
--- a/README.patches Tue Feb 10 01:31:47 2009 +0100
+++ b/README.patches Tue Feb 10 04:47:31 2009 -0200
@@ -1,5 +1,5 @@ Mauro Carvalho Chehab <mchehab at infrad
Mauro Carvalho Chehab <mchehab at infradead dot org>
- Updated on 2009 January 8
+ Updated on 2009 February 9
This file describes the general procedures used by the LinuxTV team (*)
and by the v4l-dvb community.
@@ -255,30 +255,35 @@ g) Another kernel's practice that is agr
Reviewed-by: My Name <myem...@mysite.com>
This is particularly important for Kernel to userspace ABI changes.
-h) If the patch also affects other parts of kernel (like Alsa
- or i2c), it is required that, when submitting upstream, the patch
- also goes to the maintainers of that subsystem. To do this, the
- developer shall copy the interested parties.
-
- At mercurial tree, this can be handled automatically by the LinuxTV
- scripts, by using the cc: meta tag, together with the Signed-off-by
- lines. Something like:
+h) If the patch also affects other parts of kernel (like Alsa
+ or i2c), it is required that, when submitting upstream, the patch
+ also goes to the maintainers of that subsystem. To do this, the
+ developer shall copy the interested parties.
+
+ At mercurial tree, this can be handled automatically by the LinuxTV
+ scripts, by using the cc: meta tag, together with the Signed-off-by
+ lines. Something like:
CC: someotherkerneldevelo...@someplace
Signed-off-by: nowhere <nowh...@noplace.org>
- This way, when a patch arrives mercurial hg tree, a mailbomb script
- will copy the proper interested parties.
-
- When submitting a patch via e-mail, it is better to copy all interested
- parties directly, by adding them as cc's to the email itself.
-
- Please note that those changes generally require ack from the
- other subsystem maintainers. So, the best practice is to first ask
- for their acks, then commit to the development tree or send the
- patch via email with their Acked-by: already included.
-
-i) Sometimes, mainstream changes affect the v4l-dvb tree, and mast be
+ This way, when a patch arrives mercurial hg tree, a mailbomb script
+ will copy the proper interested parties.
+
+ When submitting a patch via e-mail, it is better to copy all interested
+ parties directly, by adding them as cc's to the email itself.
+
+ Please note that those changes generally require ack from the
+ other subsystem maintainers. So, the best practice is to first ask
+ for their acks, then commit to the development tree or send the
+ patch via email with their Acked-by: already included.
+
+i) If the patch modifies the include/linux/videodev2.h file, then you
+ must also run 'make spec' to verify that the V4L2 specification
+ document still builds. Of course, any changes you make to the public
+ V4L2 API must be documented anyway.
+
+j) Sometimes, mainstream changes affect the v4l-dvb tree, and mast be
backported to the v4l-dvb tree. This kind of commit to the mercurial
tree should follow the rules above and should also have the line:
@@ -286,7 +291,7 @@ i) Sometimes, mainstream changes affect
Patches with this line will not be submitted upstream.
-j) Sometimes it is necessary to introduce some testing code inside a
+k) Sometimes it is necessary to introduce some testing code inside a
module or remove parts that are not yet finished. Also, compatibility
tests may be required to provide backporting.
@@ -319,8 +324,8 @@ j) Sometimes it is necessary to introduc
#include "mydriver-header.h"
-should be included at the
- files under v4l-dvb tree. This header also includes linux/version.h.
+ should be included at the files under v4l-dvb tree. This header also
+ includes linux/version.h.
To include testing code, #if 0 or #if 1 may be used. If this code
is meant to go also to kernel, a comment with the word "keep" should
@@ -337,7 +342,7 @@ should be included at the
See the file v4l/scripts/gentree.pl for a more complete description
of what kind of code will be kept and what kind will be removed.
-k) To import contributed stuff to a developer's, a script is provided.
+l) To import contributed stuff to a developer's, a script is provided.
This allows an easy import of mbox-based patch emails.
This is done with (called from the root tree directory):
@@ -354,7 +359,7 @@ k) To import contributed stuff to a deve
that can be applied/unapplied for testing. mailimport trusts on it to work,
so, this extension should be enabled for mailimport script to work.
-l) By submitting a patch to the subsystem maintainer, either via email
+m) By submitting a patch to the subsystem maintainer, either via email
or via pull request, the patch author(s) are agreeing that the
submitted code will be added on Kernel, and that the submitted code
are being released as GPLv2. The author may grant additional licenses
@@ -362,7 +367,7 @@ l) By submitting a patch to the subsyste
later. If no specific clause are added, the added code will be
assumed as GPLv2 only.
-m) "Commit earlier and commit often". This is a common used rule at
+n) "Commit earlier and commit often". This is a common used rule at
Kernel. This means that a sooner submission of a patch will mean that
a review can happen sooner, and help the develop to address the
comments. This helps to reduce the life-cycle for having a changeset
@@ -370,7 +375,7 @@ m) "Commit earlier and commit often". Th
changeset should ideally address just one issue. So, mixing different
things at the same patch should be avoided.
-n) Sometimes, the maintainer may need to slightly modify patches you receive
+o) Sometimes, the maintainer may need to slightly modify patches you receive
in order to merge them, because the code is not exactly the same in your
tree and the submitters'. In order to save time, it may do the changes and
add a line before his SOB, as stated on Documentation/SubmittingPatches,
---
Patch is available at:
http://linuxtv.org/hg/v4l-dvb/rev/d76f0c9b75fd4f493b55c179b4738a41b413abec
_______________________________________________
linuxtv-commits mailing list
linuxtv-commits@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linuxtv-commits
