diff options
-rw-r--r-- | README.patches | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/README.patches b/README.patches index 41b237476..87fe57be6 100644 --- a/README.patches +++ b/README.patches @@ -311,7 +311,7 @@ j) By submitting a patch to the subsystem maintainer, either via email assumed as GPLv2 only. 5. Knowing about newer patches committed at master hg repository - ============================================================ + ============================================================= There's a patchbomb script at linuxtv.org that will send one copy of each patch applied to -hg tree to: @@ -409,10 +409,13 @@ e. People will eventually comment about the patch. In this case, f. If the patch is fixing an existing maintained driver, the low-level driver maintainer will apply to his tree, and at some later - time, ask the subsystem maintainer to pull it. + time, ask the subsystem maintainer to pull it. It is a good idea to + send the patch to the maintainer C/C the mailing list for him to know + that you're expecting him to forward the patch. g. If it is a newer driver (not yet in one of the development trees), - please copy the subsystem maintainer. + please send the patch to the subsystem maintainer, C/C the proper + mailing lists. 8. Identifying regressions with Mercurial ====================================== |