From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org
Subject: Re: [patch, -rc5-mm3] lock validator: -V3
Date: Tue, 6 Jun 2006 21:33:25 +0200 [thread overview]
Message-ID: <20060606193325.GA16010@elte.hu> (raw)
In-Reply-To: <20060606091515.27db4746.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> On Tue, 6 Jun 2006 17:45:30 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
>
> > 30 files changed, 545 insertions(+), 230 deletions(-)
>
> This basically screws up the whole patch series. It'll create a
> barrier over which it will be hard to move fixups against existing
> patches.
yes. Dont worry about it, i'll refactor the whole lock validator queue
once i've done the cleanups too.
> ho-hum. Let's make sure that future patches are extremely
> fine-grained and please try to identify whether they're applicable to
> -v2 or to -v3 and we'll see how it goes.
there was just no other way to do this - this change is intrusive
independently of how finegrained the patches are.
Ingo
prev parent reply other threads:[~2006-06-06 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 15:45 [patch, -rc5-mm3] lock validator: -V3 Ingo Molnar
2006-06-06 16:15 ` Andrew Morton
2006-06-06 19:33 ` Ingo Molnar [this message]
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=20060606193325.GA16010@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox