From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] x86 updates for v2.6.28, phase #6, misc
Date: Fri, 10 Oct 2008 14:43:47 +1100 [thread overview]
Message-ID: <200810101443.48237.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20081010000817.GA9266@elte.hu>
On Friday 10 October 2008 11:08, Ingo Molnar wrote:
> out-of-topic modifications in x86-v28-for-linus-phase6:
> -------------------------------------------------------
> include/linux/kernel.h # d974ae3: generic, memparse(): constify
> arg include/linux/mm.h # f7d0b92: mm: define
> USE_SPLIT_PTLOCKS rath # 59ea746: MM: virtual address debug
> include/linux/mm_types.h # f7d0b92: mm: define USE_SPLIT_PTLOCKS
> rath include/linux/mmdebug.h # 7aa413d: x86, MM: virtual address
> debug, c # 59ea746: MM: virtual address debug lib/cmdline.c
> # d974ae3: generic, memparse(): constify arg mm/vmalloc.c
> # 7aa413d: x86, MM: virtual address debug, c # 59ea746: MM:
> virtual address debug
How come these kinds of things go into the x86 tree? Can't they
be sent to other maintainer first (probably Andrew, in the case
of random -mm stuff).
OK, it's pretty trivial stuff, but just on principle I can't see
an advantage, and only disadvantages to doing this (and also I
see the vmalloc change clashed with the vmalloc rewrite in -mm).
next prev parent reply other threads:[~2008-10-10 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 0:08 Ingo Molnar
2008-10-10 3:43 ` Nick Piggin [this message]
2008-10-10 4:18 ` Jeremy Fitzhardinge
2008-10-10 8:26 ` Ingo Molnar
2008-10-11 3:44 ` Nick Piggin
2008-10-10 18:41 ` [git pull, take 2] " Ingo Molnar
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=200810101443.48237.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome