public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Fenzi <kevin-acpi-+bl/7iUgRMUAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI source release updated (20030328)
Date: Sat, 29 Mar 2003 11:17:15 -0700	[thread overview]
Message-ID: <20030329181722.D7F0BF7E5F@voldemort.scrye.com> (raw)
In-Reply-To: 200303291811.48633.p_christ@hol.gr

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "P" == P Christeas <p_christ-U04EIuiosng@public.gmane.org> writes:

>> 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,

P> I had thought of asking that as well. But it may be a pain for
P> Andrew to make those.  If you have all the source-patches you've
P> used, you might be able to do that yourself. Just get the
P> 'original' 2.4, patch it with 2 different ver's of ACPI and diff
P> those.. Then you could apply that diff as a patch to your
P> 'overloaded' ver of 2.4.

Yeah, there is also a package out there called 'interdiff'. Lets you
make a diff between two diff files. ;) 

interdiff acpi-20030321-2.4.21-pre5.diff acpi-20030328-2.4.21-pre6.diff > acpi.diff

It seems to get one reject on the acpi patches for some reason, but
that one looks cosmetic. 

Will try it on my heavily patched 2.4.21-pre5. ;) 

kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQE+heMx3imCezTjY0ERAp8+AJ0b/uqTf4Y0A3ZOUaE5/ZyuGDAn+wCdHExQ
PWF/JMHYT1yrPlo6UUMWv9c=
=bwxy
-----END PGP SIGNATURE-----


-------------------------------------------------------
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

  reply	other threads:[~2003-03-29 18:17 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 [this message]
2003-03-29 20:45       ` the incremental patch 20030521-20030528 Sérgio Monteiro Basto
     [not found]         ` <1048970727.1944.76.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-03-29 23:52           ` 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=20030329181722.D7F0BF7E5F@voldemort.scrye.com \
    --to=kevin-acpi-+bl/7iugrmuavxtiumwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox