From: Bas Mevissen <ml-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: How to determine ACPI SF patch version from running kernel?
Date: Mon, 04 Aug 2003 11:11:03 +0200 [thread overview]
Message-ID: <3F2E2327.4050804@basmevissen.nl> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470255EEBD-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
Grover, Andrew wrote:
(ACPI_CA_VERSION)
> It changes every release, except for the most recent one. I should've
> updated it but I was in a hurry to go on vacation and didn't.
>
From acpi-20030730-2.4.22-pre8.diff.gz:
diff -Naur -X /root/bin/dontdiff a/include/acpi/acconfig.h
b/include/acpi/acconfig.h
--- a/include/acpi/acconfig.h 2003-07-30 10:06:09.000000000 -0700
+++ b/include/acpi/acconfig.h 2003-07-30 10:07:29.000000000 -0700
@@ -64,7 +64,7 @@
/* Version string */
-#define ACPI_CA_VERSION 0x20030619
+#define ACPI_CA_VERSION 0x20030714
The ACPI_CA_VERSION did change, but not to the number of the patch. My
question was how to determine the _patch_ version and not just the
version of the ACPI_CA stuff.
(Maybe I see it wrong, but I guess that ACPI_CA is just one part of the
whole patch.)
For debugging it really helps if the _patch_ number can be easely
retrieved from the source and at runtime.
For example, if you only make a change to the Toshiba-specific stuff,
then I would say keep the ACPI_CA number the same and just update the
overall patch number.
> PS this would've been a good question for acpi-support.
>
If I only were asking for _where_ to find it, it was.
Regards,
Bas.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-08-04 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 6:34 How to determine ACPI SF patch version from running kernel? Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470255EEBD-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-08-04 9:11 ` Bas Mevissen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-05 6:42 Grover, Andrew
2003-07-31 8:25 Bas Mevissen
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=3F2E2327.4050804@basmevissen.nl \
--to=ml-y9iuuvl1dgu0iwp8nzs06g@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@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