mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	Greg Kroah-Hartman <greg@kroah.com>,
	Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm)
Date: Mon, 18 Jan 2010 09:26:19 -0500	[thread overview]
Message-ID: <25759.1263824779@localhost> (raw)
In-Reply-To: Your message of "Thu, 14 Jan 2010 23:39:46 +0100." <tkrat.e8ba67441fb65247@s5r6.in-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On Thu, 14 Jan 2010 23:39:46 +0100, Stefan Richter said:
> One of the roles which -mm fulfilled some time ago (to offer an
> integration testing ground) has been taken over by -next.  This is still
> news to Documentation/HOWTO, so mention it there.

> -2.6.x -mm kernel patches
> -------------------------
> -These are experimental kernel patches released by Andrew Morton.  Andrew
> -takes all of the different subsystem kernel trees and patches and mushes
> -them together, along with a lot of patches that have been plucked from
> -the linux-kernel mailing list.  This tree serves as a proving ground for
> -new features and patches.

Note that -mm serves other purposes than just integration testing. I'm not
sure that nuking *all* reference to it is appropriate.

On the other hand, I think there's like 3 other guys besides myself that
actually test -mm kernels, so maybe the best bet is to see if it makes it
upstream via the -mm route. ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2010-01-18 14:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14  7:12 [PATCH 00/24] MAINTAINERS: Add "Q" patchwork entries Joe Perches
2010-01-14  7:13 ` [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type Joe Perches
2010-01-14 13:48   ` Stefan Richter
2010-01-14 14:02     ` Stefan Richter
2010-01-14 17:38       ` Joe Perches
2010-01-14 18:04         ` Stefan Richter
2010-01-14 18:13           ` Joe Perches
2010-01-14 18:34             ` Stefan Richter
2010-01-14 18:45               ` Joe Perches
2010-01-14 19:05                 ` Stefan Richter
2010-01-14 19:05                 ` Alan Cox
2010-01-14 19:13                   ` Joe Perches
2010-01-14 19:39                     ` Stefan Richter
2010-01-14 21:05                       ` Joe Perches
2010-01-14 22:39                         ` [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm) Stefan Richter
2010-01-14 23:36                           ` Randy Dunlap
2010-01-15  0:41                           ` Loïc Grenié
2010-01-15 12:23                             ` [PATCH update] " Stefan Richter
2010-01-18  8:25                               ` Stephen Rothwell
2010-01-18 14:26                           ` Valdis.Kletnieks [this message]
2010-01-18 15:19                             ` [PATCH] " Stefan Richter
2010-01-14 18:20           ` [PATCH] HOWTO: Point to patchwork.kernel.org and patchwork.ozlabs.org Stefan Richter
2010-01-14  7:13 ` [PATCH 02/24] MAINTAINERS: 9P FILE SYSTEM - Add "Q" patchwork entry Joe Perches
2010-01-14  7:13 ` [PATCH 03/24] MAINTAINERS: ACPI " Joe Perches
2010-01-14  7:13 ` [PATCH 04/24] MAINTAINERS: BTRFS FILE SYSTEM " Joe Perches
2010-01-14  7:13 ` [PATCH 05/24] MAINTAINERS: CIFS " Joe Perches
2010-01-14  7:13 ` [PATCH 06/24] MAINTAINERS: DEVICE-MAPPER " Joe Perches
2010-01-14  7:13 ` [PATCH 07/24] MAINTAINERS: EXT4 FILE SYSTEM " Joe Perches
2010-01-14 20:27   ` tytso
2010-01-14  7:13 ` [PATCH 08/24] MAINTAINERS: IDE SUBSYSTEM " Joe Perches
2010-01-14  7:13 ` [PATCH 09/24] MAINTAINERS: INFINIBAND " Joe Perches
2010-01-14  7:13 ` [PATCH 10/24] MAINTAINERS: INPUT DRIVERS " Joe Perches
2010-01-14  7:13 ` [PATCH 11/24] MAINTAINERS: KCONFIG " Joe Perches
2010-01-14  7:13 ` [PATCH 12/24] MAINTAINERS: LINUX FOR POWERPC " Joe Perches
2010-01-14  7:13 ` [PATCH 13/24] MAINTAINERS: V4L/DVB " Joe Perches
2010-01-14  7:13 ` [PATCH 14/24] MAINTAINERS: MTD " Joe Perches
2010-01-14  7:13 ` [PATCH 15/24] MAINTAINERS: NETWORKING [WIRELESS] " Joe Perches
2010-01-14  7:13 ` [PATCH 16/24] MAINTAINERS: OMAP " Joe Perches
2010-01-19 18:11   ` Tony Lindgren
2010-01-14  7:13 ` [PATCH 17/24] MAINTAINERS: PARISC ARCHITECTURE " Joe Perches
2010-01-14  7:13 ` [PATCH 18/24] MAINTAINERS: PCI SUBSYSTEM " Joe Perches
2010-01-14  7:13 ` [PATCH 19/24] MAINTAINERS: REAL TIME CLOCK " Joe Perches
2010-01-14  7:13 ` [PATCH 20/24] MAINTAINERS: TI DAVINCI " Joe Perches
2010-01-14  7:13 ` [PATCH 21/24] MAINTAINERS: SPARC " Joe Perches
2010-01-14  7:13 ` [PATCH 22/24] MAINTAINERS: SPI SUBSYSTEM " Joe Perches
2010-01-14 13:38   ` Grant Likely
2010-01-14  7:13 ` [PATCH 23/24] MAINTAINERS: SUPERH " Joe Perches
2010-01-14  7:13 ` [PATCH 24/24] MAINTAINERS: THE REST (LKML) " Joe Perches
2010-01-14 17:24 ` [PATCH 00/24] MAINTAINERS: Add "Q" patchwork entries David Daney
2010-01-14 17:40   ` Joe Perches

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=25759.1263824779@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome