From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 3/10] Documentation/development-process: add staging & mmotm info
Date: Mon, 17 May 2010 16:21:11 -0700 [thread overview]
Message-ID: <12741384712276@xenotime.net> (raw)
In-Reply-To: <12741384711166@xenotime.net>
From: Randy Dunlap <randy.dunlap@oracle.com>
Update explanation of mmotm.
Add explanation of drivers/staging/.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Acked-by: Jonathan Corbet <corbet@lwn.net>
---
Documentation/development-process/2.Process | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
--- lnx-2634-docs.orig/Documentation/development-process/2.Process
+++ lnx-2634-docs/Documentation/development-process/2.Process
@@ -267,12 +267,8 @@ an appropriate subsystem tree or be sent
development cycle, approximately 10% of the patches going into the mainline
get there via -mm.
-The current -mm patch can always be found from the front page of
-
- http://kernel.org/
-
-Those who want to see the current state of -mm can get the "-mm of the
-moment" tree, found at:
+The current -mm patch is available in the "mmotm" (-mm of the moment)
+directory at:
http://userweb.kernel.org/~akpm/mmotm/
@@ -307,6 +303,12 @@ volatility of linux-next tends to make i
See http://lwn.net/Articles/289013/ for more information on this topic, and
stay tuned; much is still in flux where linux-next is involved.
+Besides the mmotm and linux-next trees, the kernel source tree now contains
+the drivers/staging/ directory and many sub-directories for drivers or
+filesystems that are on their way to being added to the kernel tree
+proper, but they remain in drivers/staging/ while they still need more
+work.
+
2.5: TOOLS
--
next prev parent reply other threads:[~2010-05-17 23:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 23:21 [PATCH 0/10] documentation patch queue for 2.6.35 merge window Randy Dunlap
2010-05-17 23:21 ` [PATCH 5/10] Documentation/timers/hpet_example: drop duplicate header files Randy Dunlap
2010-05-17 23:21 ` [PATCH 4/10] Documentation/sysrq.txt: update KEY_SYSRQ info Randy Dunlap
2010-05-17 23:21 ` [PATCH 8/10] scsi_scan.c: fix/convert functions to use kernel-doc Randy Dunlap
2010-05-17 23:21 ` Randy Dunlap [this message]
2010-05-17 23:21 ` [PATCH 6/10] Documentation/vm: use better value for MAP_HUGETLB Randy Dunlap
2010-05-17 23:21 ` [PATCH 7/10] scsi: update torque.net references to current location Randy Dunlap
2010-05-17 23:21 ` [PATCH 10/10] Documentation: update SubmitChecklist for O=objdir and kconfig testing Randy Dunlap
2010-05-17 23:21 ` [PATCH 1/10] docbook: make mtd nand module init static Randy Dunlap
2010-05-17 23:21 ` [PATCH 9/10] fusion: fix kernel-doc notation Randy Dunlap
2010-05-17 23:21 ` [PATCH 2/10] Documentation/development-process: add maintainers and git info Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12741384712276@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.