From: "Sérgio Monteiro Basto" <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
To: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
Cc: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: the incremental patch 20030521-20030528
Date: 29 Mar 2003 20:45:26 +0000 [thread overview]
Message-ID: <1048970727.1944.76.camel@darkstar.portugal> (raw)
In-Reply-To: <20030329151604.GA19676-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
Make the incremental patch is easy: apply the old patch to kernel and
the new patch to a copy of same kernel version, clean orig (and rej)
files and make the diff -Nur.
so here is the result, and don't test is yet.
On Sat, 2003-03-29 at 15:16, Karol Kozimor wrote:
> Thus wrote Grover, Andrew:
> > Fixed a problem where the error message "Failed to acquire semaphore"
> > would appear during operations on the embedded controller (EC).
>
> Thanks for that!
> I have one question though. Did you consider doing incremental ACPI
> patches? I'm using a heavily patched kernel with XFS filesystem support,
> and getting all these patches to work and applying all the rejects manually
> is a real pain. Incremental patches would really make life (mine, at least)
> easier. What do you think about it?
>
> (the above refers to the 2.4 kernel, with 2.5 changing so fast it isn't
> really a problem)
>
> Best regards,
>
> --
> Karol 'sziwan' Kozimor
> sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
--
SérgioMB
email: sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org
Who gives me one shell, give me everything.
[-- Attachment #2: 05210528.diff.gz --]
[-- Type: application/x-gzip, Size: 6259 bytes --]
next prev parent reply other threads:[~2003-03-29 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 0:01 ACPI source release updated (20030328) Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847E96D8E-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-03-29 15:16 ` Karol Kozimor
[not found] ` <20030329151604.GA19676-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-03-29 16:11 ` P. Christeas
2003-03-29 18:17 ` Kevin Fenzi
2003-03-29 20:45 ` Sérgio Monteiro Basto [this message]
[not found] ` <1048970727.1944.76.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-03-29 23:52 ` Re: the incremental patch 20030521-20030528 Sérgio Monteiro Basto
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=1048970727.1944.76.camel@darkstar.portugal \
--to=sergiomb-hho3weeoaswvhhzd4jos4w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox