All of lore.kernel.org
 help / color / mirror / Atom feed
From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Kernelnewbies@kernelnewbies.org
Subject: Re: 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 20:24:53 +0800	[thread overview]
Message-ID: <CAAvDm6YjbvEq9Y3wG-Lx_-hJtQ_LW28j97BOqvrewYXnEAS2dg@mail.gmail.com> (raw)
In-Reply-To: <20200701105824.GB2098169@kroah.com>


[-- Attachment #1.1: Type: text/plain, Size: 146 bytes --]

Hi, Gred
Thank you for taking the time to respond to me.
>> Would it do harm to the hardware?
> It might, try it and see :)
It's really bad news.

[-- Attachment #1.2: Type: text/html, Size: 387 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

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

  reply	other threads:[~2020-07-01 12:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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  9:15 ` 孙世龙 sunshilong
2020-07-01 10:58 ` Greg KH
2020-07-01 10:58   ` Greg KH
2020-07-01 12:24   ` 孙世龙 sunshilong [this message]
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=CAAvDm6YjbvEq9Y3wG-Lx_-hJtQ_LW28j97BOqvrewYXnEAS2dg@mail.gmail.com \
    --to=sunshilong369@gmail.com \
    --cc=Kernelnewbies@kernelnewbies.org \
    --cc=greg@kroah.com \
    --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.