From: Martin Bligh <mbligh@google.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, apw@shadowen.org, greg@kroah.com
Subject: Re: Problems with 2.6.15-mm1 and mm2.
Date: Mon, 09 Jan 2006 16:50:47 -0800 [thread overview]
Message-ID: <43C304E7.7000508@google.com> (raw)
In-Reply-To: <20060109164653.23b2676e.akpm@osdl.org>
>> Below is cut & pasted, so not applyable, and maybe it shouldn't be
>> applied. But ... it worked before whatever is in -mm ... so my personal
>> feeling is that if we don't have a fix for whatever is currently in -mm,
>> it should get dropped until we do ? Going backwards = bad.
>>
>> Perhaps I'm in a time loop, and just confused. but I don't think so ?
>
>
> This isn't at all clear, sorry.
>
> Does the patch you sent fix things in 2.6.15-mm2? On NUMAQ and on x86_64?
> Does it fix a bug which was introduced in a patch which in in 2.6.15-mm2?
> If so, which one?
It fixes the symptom, yes. Greg complained it's papering over the
problem and not a real fix, which is fair enough, but ...
yes, it did seem to be a newly introduced problem in -mm1 or -mm2. To my
mind, if we don't have a proper fix, we ought to drop the patch that
caused the problem in the first place? Andy .. can you finger which
patch that was, I forget ...
M.
next prev parent reply other threads:[~2006-01-10 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 17:59 Problems with 2.6.15-mm1 and mm2 Martin Bligh
2006-01-09 23:41 ` Andrew Morton
2006-01-10 0:05 ` Martin Bligh
2006-01-10 0:46 ` Andrew Morton
2006-01-10 0:50 ` Martin Bligh [this message]
2006-01-10 14:52 ` Andy Whitcroft
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=43C304E7.7000508@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=greg@kroah.com \
--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.