From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Linux/ACPI 2.4 release status and cpufreq
Date: Mon, 15 Dec 2003 15:08:07 +0100 [thread overview]
Message-ID: <3FDDC047.9070105@pca.it> (raw)
In-Reply-To: <20031215125917.0eca2dc1.subscript-GANU6spQydw@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 12/15/03 12:59, wwp wrote:
| Using cpufreq-LINUX_2_4-20031215.tar.bz2, patching manually
| w/ `patch -p1 --dry-run < patch` against a 2.4.33+acpi+ieee1394+
| other-various-patches:
this sounds quite strange, because here:
| gismo:/usr/src/linux-2.4.23# patch -p1 --dry-run <
cpufreq-LINUX_2_4-20031215.tar.bz2
| patch unexpectedly ends in middle of line
| patch: **** Only garbage was found in the patch input.
| gismo:/usr/src/linux-2.4.23#
of the same
| gismo:/usr/src/linux-2.4.23# patch -p1 --dry-run <
cpufreq-LINUX_2_4-20031215.tar
| missing header for unified diff at line 57 of patch
| patching file Documentation/00-INDEX
| patching file Documentation/Configure.help
| patching file Makefile
| patching file arch/i386/boot/setup.S
| patching file arch/i386/config.in
| patching file arch/i386/kernel/Makefile
| patching file arch/i386/kernel/i386_ksyms.c
| patching file arch/i386/kernel/setup.c
| patching file arch/i386/kernel/time.c
| patching file drivers/Makefile
| patching file include/asm-i386/ist.h
| patching file include/asm-i386/msr.h
| patching file include/asm-i386/smp.h
| patching file include/linux/smp.h
| patch unexpectedly ends in middle of line
| gismo:/usr/src/linux-2.4.23#
Anyway, I made some tests:
- - I've always the problem above if I use the command
bunzip2/gunzip -c [patch].bz2/gz | patch -p1
- - if I bunzip2/gunzip + untar (so 'tar xvf[j|z]') and then I use the
manual patching script present in the 'cpufreq' package, all goes well
As this is the only patch which doesn't work on my system, I think
there's a problem in the patch, but maybe as I'm on Debian unstable,
there could be some bugs on my machine.
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQE/3cBGVAp7Xm10JmkRAgqeAJ42124ybVwEjgiXy0VBpYVP7T8ieACffhZZ
hMhWLK57AiBrqz5vLTE/Qfw=
=ta8/
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-15 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 1:26 Linux/ACPI 2.4 release status and cpufreq Ow Mun Heng
[not found] ` <C386328088ED7F4E9F81AFBABDDF60DA0378C85A-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
2003-12-15 8:01 ` wwp
2003-12-15 11:26 ` Micha Feigin
[not found] ` <20031215112626.GB5898-4cxDFgrrBECgSpxsJD1C4w@public.gmane.org>
2003-12-15 11:42 ` Luca Capello
[not found] ` <3FDD9E37.2090307-wlebWZzHoyE@public.gmane.org>
2003-12-15 11:59 ` wwp
[not found] ` <20031215125917.0eca2dc1.subscript-GANU6spQydw@public.gmane.org>
2003-12-15 14:08 ` Luca Capello [this message]
[not found] ` <3FDDC047.9070105-wlebWZzHoyE@public.gmane.org>
2003-12-15 14:40 ` Karol Kozimor
2003-12-15 16:11 ` Micha Feigin
2003-12-15 16:06 ` Micha Feigin
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 9:14 Yu, Luming
2003-12-16 1:35 Ow Mun Heng
2003-12-15 8:15 Ow Mun Heng
2003-12-12 6:15 Linux/ACPI 2.4 release status Len Brown
[not found] ` <1071209752.2542.688.camel-D2Zvc0uNKG8@public.gmane.org>
2003-12-12 17:06 ` Linux/ACPI 2.4 release status and cpufreq Sérgio Monteiro Basto
[not found] ` <1071248784.1756.7.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-12-12 20:20 ` Karol Kozimor
2003-12-15 18:08 ` Ducrot Bruno
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=3FDDC047.9070105@pca.it \
--to=luca-wlebwzzhoye@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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.