diff options
| author | Varun Wadekar <vwadekar@nvidia.com> | 2012-07-30 18:22:08 +0530 |
|---|---|---|
| committer | Varun Wadekar <vwadekar@nvidia.com> | 2012-07-30 18:22:08 +0530 |
| commit | 0d9666218f30f9f53cd04c09adbd2d9060c3beef (patch) | |
| tree | 49b5d9de126019a1fa983ed4d5b95b10aca3626e /Documentation | |
| parent | 4cc8fa40b89a47cba1b38a6ae974e3a0670d050d (diff) | |
| parent | 1811650b54e3d988dfd6dc9ecb8c7d0e4986d8a1 (diff) | |
Merge remote-tracking branch 'origin/android-tegra-nv-3.1' into android-t114-3.4
NULL merge from android-tegra-nv-3.1
Change-Id: I8c49e4b9df6820eb1ad7edca2233982a6c4043d8
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/HOWTO | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/Documentation/HOWTO b/Documentation/HOWTO index 59c080f084ef..c9400a43abd4 100644 --- a/Documentation/HOWTO +++ b/Documentation/HOWTO @@ -11,7 +11,6 @@ If anything in this document becomes out of date, please send in patches to the maintainer of this file, who is listed at the bottom of the document. - Introduction ------------ @@ -52,7 +51,6 @@ possible about these standards ahead of time, as they are well documented; do not expect people to adapt to you or your company's way of doing things. - Legal Issues ------------ @@ -66,7 +64,6 @@ their statements on legal matters. For common questions and answers about the GPL, please see: http://www.gnu.org/licenses/gpl-faq.html - Documentation ------------ @@ -187,7 +184,7 @@ apply a patch. If you do not know where you want to start, but you want to look for some task to start doing to join into the kernel development community, go to the Linux Kernel Janitor's project: - http://kernelnewbies.org/KernelJanitors + http://kernelnewbies.org/KernelJanitors It is a great place to start. It describes a list of relatively simple problems that need to be cleaned up and fixed within the Linux kernel source tree. Working with the developers in charge of this project, you @@ -250,10 +247,10 @@ process is as follows: release a new -rc kernel every week. - Process continues until the kernel is considered "ready", the process should last around 6 weeks. - - Known regressions in each release are periodically posted to the - linux-kernel mailing list. The goal is to reduce the length of + - Known regressions in each release are periodically posted to the + linux-kernel mailing list. The goal is to reduce the length of that list to zero before declaring the kernel to be "ready," but, in - the real world, a small number of regressions often remain at + the real world, a small number of regressions often remain at release time. It is worth mentioning what Andrew Morton wrote on the linux-kernel |