All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allen Chan <alydar@users.sourceforge.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Incremental patches available
Date: Fri, 30 Jul 2004 19:24:02 -0400	[thread overview]
Message-ID: <200407301924.04914.alydar@users.sourceforge.net> (raw)

While attempting to build and test a 2.6.7 kernel including the 
patches found on the new incremental patches page, I've bumped into 
into problems with a couple of the patches:

(1)  remap - apparently, this patch has already been applied as part 
of  uml-patch-2.6.7-1.bz2.
(2)  time - one of the patches included here attempts to modify 
um/arch/um/os/Makefile.  However, that file does not exist.  It looks 
like that file should be um/arch/um/os-Linux/Makefile.

The rest of the 2.6.7 patches (other than hostfs which the website 
says "*** This currently doesn't compile ***") appear to apply with 
no problems.

Now to compile and beat up on the new test kernel...


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2004-07-30 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 23:24 Allen Chan [this message]
2004-07-31  5:02 ` [uml-devel] Re: Incremental patches available Jeff Dike
2004-08-02 18:04   ` Allen Chan

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=200407301924.04914.alydar@users.sourceforge.net \
    --to=alydar@users.sourceforge.net \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.