From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: fix init_memory_mapping for [dc000000 - e0000000)
Date: Tue, 28 Oct 2008 21:14:59 +0300 [thread overview]
Message-ID: <20081028181459.GC7357@localhost> (raw)
In-Reply-To: <20081028181004.GA11275@elte.hu>
[Ingo Molnar - Tue, Oct 28, 2008 at 07:10:04PM +0100]
|
| * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
|
| > [Ingo Molnar - Tue, Oct 28, 2008 at 10:27:37AM +0100]
| > |
| > | * Yinghai Lu <yinghai@kernel.org> wrote:
| > |
| > | > Impact: fix range calculation
| > |
| > | applied to tip/x86/urgent, thanks Yinghai!
| > |
| > | i changed the impact line to:
| > |
| > | Impact: change over-mapping to precise mapping, fix /proc/meminfo output
| > |
| > | Ingo
| > |
| >
| > When we started to use Impact: line? I mean -- now we have
| > to use it? Just noticed this word in patches a day or maybe
| > several day ago -- so it seem to be quite freshy :)
|
| We've been experimenting with the impact-line for a couple of
| weeks/months, just to see how it works out in practice.
|
| The first impact-line ever was added by hpa in mid-summer:
|
| | commit 908ec7afacfdc83dc10938ed1d3c38b3526034ec
| | Author: H. Peter Anvin <hpa@zytor.com>
| | Date: Mon Jun 30 14:42:18 2008 -0700
| |
| | x86: remove arbitrary ELF section limit in i386 relocatable kernel
| |
| | Impact: build failure in maximal configurations
|
| The concept seems to be quite good in general:
|
| - increases the readability of the changlogs
|
| - makes it easier to judge the backporting needs of a commit, even
| if a commit has not been marked as Cc: <stable@kernel.org> straight
| away.
|
| - makes it easier to notice bugs in a commit: when a commit marked as
| "Impact: cleanup" causes some behavioral change it's clear that
| it's buggy.
|
| It basically acts as a second-level subject line.
|
| So, given these many advantages, we now try to extend the use of
| impact-lines to all the tip/*/urgent branches.
|
| It's not a must-have item for patch submissions, just a nice-to-have
| property. (we'll add the impact-line when it's missing)
|
| Ingo
|
Ingo, I think it's a subject for SubmittingPatches then. To
eliminate future possible questions for those who never saw it
before. Thanks for explanation!
- Cyrill -
next prev parent reply other threads:[~2008-10-28 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 5:58 [PATCH] x86: keep the page count correct Yinghai Lu
2008-10-27 16:50 ` Suresh Siddha
2008-10-27 17:55 ` Ingo Molnar
2008-10-28 1:52 ` [PATCH] x86: fix init_memory_mapping for [dc000000 - e0000000) Yinghai Lu
2008-10-28 9:27 ` Ingo Molnar
2008-10-28 17:48 ` Cyrill Gorcunov
2008-10-28 18:10 ` Ingo Molnar
2008-10-28 18:14 ` Cyrill Gorcunov [this message]
2008-10-28 18:18 ` Ingo Molnar
2008-10-28 18:22 ` Cyrill Gorcunov
[not found] ` <20081028093930.GA9699@elte.hu>
[not found] ` <20081028094758.GA11958@elte.hu>
[not found] ` <4906E048.6060006@kernel.org>
[not found] ` <20081028095244.GY15734@elte.hu>
2008-10-28 19:39 ` [PATCH] x86: fix init_memory_mapping for [dc000000 - e0000000) - v2 Yinghai Lu
2008-10-28 19:55 ` 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=20081028181459.GC7357@localhost \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).