From: Ducrot Bruno <ducrot@arm.linux.org.uk>
To: cpufreq@www.linux.org.uk
Subject: cpufreq patchin.sh,1.1.1.7,1.1.1.8
Date: Tue, 04 Jan 2005 09:18:40 +0000 [thread overview]
Message-ID: <E1Clkps-0002rA-CU@flint.arm.linux.org.uk> (raw)
Update of /mnt/src/cvsroot/cpufreq
In directory flint:/tmp/cvs-serv10975/cpufreq
Modified Files:
Tag: LINUX_2_4
patchin.sh
Log Message:
From Sergio Monteiro Basto:
more than trivial
Documentation , not Docmuentation.
This clean one warning when apply for 2nd time on same kernel.
Index: patchin.sh
===================================================================
RCS file: /mnt/src/cvsroot/cpufreq/patchin.sh,v
retrieving revision 1.1.1.7
retrieving revision 1.1.1.8
diff -u -r1.1.1.7 -r1.1.1.8
--- patchin.sh 26 Aug 2004 16:11:27 -0000 1.1.1.7
+++ patchin.sh 4 Jan 2005 09:18:37 -0000 1.1.1.8
@@ -14,7 +14,7 @@
exit 1
fi
-rm -rf $cpufreq/linux/Docmuentation/cpu-freq
+rm -rf $cpufreq/linux/Documentation/cpu-freq
ln -sf cpufreq $cpufreq/linux/Documentation/cpu-freq
diff -Nur -x"*CVS*" $1/Documentation/cpu-freq linux/Documentation/cpu-freq > patch_core
reply other threads:[~2005-01-04 9:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Clkps-0002rA-CU@flint.arm.linux.org.uk \
--to=ducrot@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
/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