From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Cc: linuxsh-dev@lists.sourceforge.net
Subject: Re: [PATCH] Preemptible kernel for SH
Date: 01 Dec 2001 22:28:36 -0500 [thread overview]
Message-ID: <1007263717.956.7.camel@phantasy> (raw)
In-Reply-To: <1007261428.820.4.camel@phantasy>
In-Reply-To: <1007261428.820.4.camel@phantasy>
ftp://ftp.kernel.org/pub/linux/kernel/people/rml/sh/sh-update-rml-2.4.16-1.patch
I went ahead and diffed 2.4.16 against the SH tree. Thus you can patch
2.4.16 directly without checking into CVS. Hopefully this might
encourage some testers.
ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.16-1.patch
ftp://ftp.kernel.org/pub/linux/kernel/people/rml/sh/preempt-kernel-sh-2.4.16-1.patch
The above is links to the preempt-kernel patch and the arch-sh specific
work.
Users need to patch 2.4.16 with the three patches above and enable
CONFIG_PREEMPT to create the preemptible kernel for SH.
Robert Love
next prev parent reply other threads:[~2001-12-02 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 2:50 [PATCH] Preemptible kernel for SH Robert Love
2001-12-02 3:28 ` Robert Love [this message]
2001-12-03 21:16 ` [linuxsh-dev] " Jeremy Siegel
2001-12-03 22:18 ` Robert Love
2001-12-05 22:22 ` Robert Love
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=1007263717.956.7.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox