merge: v4l-dvb

1 files changed, 16 insertions, 20 deletions

diff --git a/README.patches b/README.patches
index 785a67819..931c15960 100644
--- a/README.patches
+++ b/README.patches
@@ -1,5 +1,5 @@
 Mauro Carvalho Chehab <mchehab at infradead dot org>
-					Updated on 2008 August, 5
+					Updated on 2009 January 8
 
 This file describes the general procedures used by the LinuxTV team (*)
 and by the v4l-dvb community.
@@ -57,7 +57,10 @@ The main kernel trees is owned by Linus Torvalds, being located at:
 
 The subsystem master tree is owned by the subsystem maintainer (Mauro
 Carvalho Chehab) being located at:
-	http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git
+	http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-2.6.git
+A tree with development patches that aren't ready yet for upstream is
+handled at:
+	http://git.kernel.org/?p=linux/kernel/git/mchehab/devel.git
 
 There's also an experimental tree, that contains all experimental patches
 from subsystem trees. It is called linux-next. Its purpose is to check in
@@ -162,16 +165,16 @@ b) All commits at mercurial trees should have a consistent message,
    From: line shouldn't be omitted, since it will be used for the
    patch author when converting to -git.
 
-   Priority: meta-tag will be used as a hint to the subsystem maintainer, to help him to 
-   identify if the patch is an improvement or board addition ("normal"), that will follow 
-   the normal lifecycle of a patch (e.g. will be sent upstream on the next merge tree), if 
+   Priority: meta-tag will be used as a hint to the subsystem maintainer, to help him to
+   identify if the patch is an improvement or board addition ("normal"), that will follow
+   the normal lifecycle of a patch (e.g. will be sent upstream on the next merge tree), if
    the patch is a bug fix tree for a while without merging upstream ("low").
 
    Valid values for "Priority:" are "low", "normal" and "high".
 
-c) All patches are requested to have their coding style validated by using 
-   script/checkpatch.pl. This check runs automatically by using "make commit". By default, 
-   it will try to use the newest version of the script, between the kernel one and a copy 
+c) All patches are requested to have their coding style validated by using
+   script/checkpatch.pl. This check runs automatically by using "make commit". By default,
+   it will try to use the newest version of the script, between the kernel one and a copy
    at v4l-dvb development tree.
 
    It is always a good idea to use in-kernel version, since additional tests
@@ -474,19 +477,12 @@ procedure to have a patch accepted in the v4l/dvb subsystem and in the
 kernel is the following:
 
 a. Post your patches to the corresponding mailing list for review and
-   test by other people.
+   test by other people, at:
+	linux-media@vger.kernel.org
 
-   For analog or core changes, the V4L mailing list is
-	video4linux-list on redhat.com
-
-   For DVB changes, the mailing list is
-	linux-dvb on linuxtv.org
-
-   PS.: Sending emails to DVB Mailing List requires subscription via
-	http://linuxtv.org/lists.php
-
-	V4L mailing list doesn't require subscription, although
-	  subscription is recommended.
+	This mailing list doesn't require subscription, although
+	it is recommended to subscribe, expecially if you're
+	developing V4L/DVB drivers.
 
 b. Use [PATCH] and a brief description in the email's subject.
    This will help the LinuxTV team to better handle it.