summaryrefslogtreecommitdiff
path: root/README.patches
diff options
context:
space:
mode:
Diffstat (limited to 'README.patches')
-rw-r--r--README.patches16
1 files changed, 8 insertions, 8 deletions
diff --git a/README.patches b/README.patches
index 4634b8b99..931c15960 100644
--- a/README.patches
+++ b/README.patches
@@ -58,7 +58,7 @@ 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/linux-2.6.git
-A tree with development patches that aren't ready yet for upstream is
+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
@@ -165,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
@@ -481,7 +481,7 @@ a. Post your patches to the corresponding mailing list for review and
linux-media@vger.kernel.org
This mailing list doesn't require subscription, although
- it is recommended to subscribe, expecially if you're
+ 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.