All of lore.kernel.org
 help / color / mirror / Atom feed
From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Kernelnewbies@kernelnewbies.org, linux-kernel@vger.kernel.org
Subject: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
Date: Wed, 1 Jul 2020 17:15:52 +0800	[thread overview]
Message-ID: <CAAvDm6bGBbN=EiJxO9Fq9HqLz6F=hSQqjKms_G6qPHzbZ6G3zg@mail.gmail.com> (raw)

Hi, list

Are there some potentially serious problems that I should be aware of
if I totally disable the CONFIG_ACPI option on the X86_64 platform?

Would it do harm to the hardware?

Thank you for your attention to this matter.

WARNING: multiple messages have this Message-ID (diff)
From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Kernelnewbies@kernelnewbies.org, linux-kernel@vger.kernel.org
Subject: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
Date: Wed, 1 Jul 2020 17:15:52 +0800	[thread overview]
Message-ID: <CAAvDm6bGBbN=EiJxO9Fq9HqLz6F=hSQqjKms_G6qPHzbZ6G3zg@mail.gmail.com> (raw)

Hi, list

Are there some potentially serious problems that I should be aware of
if I totally disable the CONFIG_ACPI option on the X86_64 platform?

Would it do harm to the hardware?

Thank you for your attention to this matter.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2020-07-01  9:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01  9:15 孙世龙 sunshilong [this message]
2020-07-01  9:15 ` Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform? 孙世龙 sunshilong
2020-07-01 10:58 ` Greg KH
2020-07-01 10:58   ` Greg KH
2020-07-01 12:24   ` 孙世龙 sunshilong
2020-07-01 12:28     ` 孙世龙 sunshilong
2020-07-01 12:28       ` 孙世龙 sunshilong
2020-07-19  4:38   ` 孙世龙 sunshilong
2020-07-19  4:38     ` 孙世龙 sunshilong
2020-07-04 12:22 ` Pavel Machek
2020-07-04 12:22   ` Pavel Machek
2020-07-04 13:34   ` 孙世龙 sunshilong
2020-07-04 13:34     ` 孙世龙 sunshilong
2020-07-04 20:09     ` Pavel Machek
2020-07-04 20:09       ` Pavel Machek
2020-07-05  1:47       ` 孙世龙 sunshilong
2020-07-05  1:47         ` 孙世龙 sunshilong
2020-07-19  5:03   ` 孙世龙 sunshilong
2020-07-19  5:03     ` 孙世龙 sunshilong

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='CAAvDm6bGBbN=EiJxO9Fq9HqLz6F=hSQqjKms_G6qPHzbZ6G3zg@mail.gmail.com' \
    --to=sunshilong369@gmail.com \
    --cc=Kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.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.