mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Heler <lkml@lpbproductions.com>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8-rc3-np1
Date: Wed, 11 Aug 2004 16:04:29 -0700	[thread overview]
Message-ID: <200408111604.30739.lkml@lpbproductions.com> (raw)
In-Reply-To: <1092262435.8976.59.camel@nosferatu.lan>

This applied fine here with some tweaking. Removing the nmi fixes from the np 
patch allowed it to apply just fine with some offsets , but not fuzz.

Matt



On Wednesday 11 August 2004 3:13 pm, Martin Schlemmer wrote:
> On Mon, 2004-08-09 at 11:52, Nick Piggin wrote:
> > http://www.kerneltrap.org/~npiggin/2.6.8-rc3-np1/
> >
> > Patch is against 2.6.8-rc3-mm2 only at this stage due to significant
> > memory management changes in there making it difficult to track Linus'
> > tree as well.
> >
> > Feedback on the scheduler would be much appreciated, as it might get
> > a run in Andrew's tree soon.
>
> I am trying to get it patched against rc4-mm1, but it seems there
> are some issues with the SMT bits - dependent_sleeper for example
> is still around although it was removed with all previous patches
> (and uses task_t.time_slice which is no longer there).
>
> I assume you forgot to apply them?  Possible to get a complete
> patch?  If not, I'll see if I can get something going after some
> sleep.
>
>
> Thanks,

  reply	other threads:[~2004-08-11 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09  9:52 2.6.8-rc3-np1 Nick Piggin
2004-08-10 17:31 ` 2.6.8-rc3-np1 Jason Munro
2004-08-11 22:13 ` 2.6.8-rc3-np1 Martin Schlemmer
2004-08-11 23:04   ` Matt Heler [this message]
2004-08-12  4:42     ` 2.6.8-rc3-np1 Martin Schlemmer
2004-08-12  7:11   ` 2.6.8-rc3-np1 Nick Piggin

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=200408111604.30739.lkml@lpbproductions.com \
    --to=lkml@lpbproductions.com \
    --cc=azarah@nosferatu.za.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lpbproduction.scom \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®