From: Russell King <rmk@arm.linux.org.uk>
To: Francesco Poli <frx@firenze.linux.it>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Wed, 7 Apr 2004 08:11:33 +0100 [thread overview]
Message-ID: <20040407081133.B2196@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040406230134.01c2e4b3.frx@firenze.linux.it>; from frx@firenze.linux.it on Tue, Apr 06, 2004 at 11:01:34PM +0200
On Tue, Apr 06, 2004 at 11:01:34PM +0200, Francesco Poli wrote:
> Wouldn't some shell commands like
>
> tar xzvfp cpufreq-...tar.gz
> cd cpufreq
> ./patchin.sh /path/to/kernel/sources
>
> suffice?
> I am quoting Bruno Ducrot's instructions... but maybe I don't catch
> something important...
That assumes that the CVS has been kept up to date with the latest 2.4
kernel.
> I'm sorry: I didn't realize you were /so/ short of space... :-(
Well, last nights generation of the CVS snapshot has failed due to lack
of disk space.
As I've said, this was meant to be solved by a replacement machine, and
had that replacement machine not been lost by the parcel carrier, it
would've been on line by now.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-04-07 7:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:42 Help with Installation Ozeki San
2004-04-03 14:50 ` Bruno Ducrot
2004-04-03 15:16 ` Francesco Poli
2004-04-03 16:22 ` Russell King
2004-04-04 17:57 ` Francesco Poli
2004-04-04 21:11 ` Dominik Brodowski
2004-04-05 20:20 ` Francesco Poli
2004-04-05 21:06 ` Russell King
2004-04-06 21:01 ` Francesco Poli
2004-04-07 7:11 ` Russell King [this message]
2004-04-07 20:26 ` Francesco Poli
2004-04-05 21:11 ` Dominik Brodowski
2004-04-06 8:25 ` Bruno Ducrot
2004-04-06 8:47 ` Bruno Ducrot
2004-04-06 21:50 ` Francesco Poli
2004-04-07 16:18 ` Bruno Ducrot
2004-04-06 21:48 ` Francesco Poli
2004-04-06 22:00 ` Dominik Brodowski
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=20040407081133.B2196@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=frx@firenze.linux.it \
/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