From: Bas Mevissen <ml-Y9IUUvl1dgU0Iwp8Nzs06g@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: How to determine ACPI SF patch version from running kernel?
Date: Thu, 31 Jul 2003 10:25:16 +0200 [thread overview]
Message-ID: <3F28D26C.70803@basmevissen.nl> (raw)
Hi all,
(I hope this is not asked before, but the SF mailing list archives are
not searchable, so I was not able to search really well)
How can I determine the ACPI SF patch number? In the ACPI sources there
are a few numbers used:
ACPI_CA_VERSION
TOSHIBA_ACPI_VERSION
etc.
Those version numbers tell me the versions of the different modules
within ACPI. If I understand it correctly, there is currently no way to
determine the "overall" ACPI patch version (aka the SF patch version)
from a running kernel and possibly not even from the sources without
using the time stamp.
If so, I think it should change. Otherwise, please tell me how to
determine this from the kernels syslog.
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 reply other threads:[~2003-07-31 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 8:25 Bas Mevissen [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2003-08-05 6:42 Grover, Andrew
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=3F28D26C.70803@basmevissen.nl \
--to=ml-y9iuuvl1dgu0iwp8nzs06g@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