From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.0test5: 2 of 3] MCA/TLB recovery
Date: Wed, 08 Oct 2003 23:31:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106565591808349@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106522368223247@msgid-missing>
>>>>> On Wed, 8 Oct 2003 15:45:16 -0700, jbarnes@sgi.com (Jesse Barnes) said:
Jesse> Really, even for ia64 code?
Yes, Linus was very clear that the bug-fix-only applies to the entire
kernel, including all platform-specific code.
Jesse> Does that mean all the changes I've recently pushed you will
Jesse> be dropped? What about the fix for CONFIG_DISCONTIGMEM +
Jesse> CONFIG_VIRTUAL_MEM_MAP that I've been working so hard to
Jesse> clean up?
If it's a bug fix, it should be OK (for some definition of "bug").
But we may have to expend some extra effort to make it _really_ a bug
fix only.
--david
prev parent reply other threads:[~2003-10-08 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 23:27 [PATCH 2.6.0test5: 2 of 3] MCA/TLB recovery Luck, Tony
2003-10-08 20:51 ` David Mosberger
2003-10-08 21:44 ` Luck, Tony
2003-10-08 22:39 ` David Mosberger
2003-10-08 22:45 ` Jesse Barnes
2003-10-08 23:31 ` David Mosberger [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=marc-linux-ia64-106565591808349@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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.