On Wed, Nov 13, 2019 at 4:59 AM Konstantin Andreev wrote:
>
> I have looked into the sources of the kernel 4.19.13.
>
> After the series of checks the fcntl(F_SETFL) just stores flags into the file
> descriptor, and that's all:
Ack, thanks. I did not think the kernel discarded the data when
swit
Hi, Jeffrey.
I have looked into the sources of the kernel 4.19.13.
After the series of checks the fcntl(F_SETFL) just stores flags into the file
descriptor, and that's all:
fs/fcntl.c:
| int setfl(int fd, struct file * filp, unsigned long arg)
| {
| int error = 0;
| ...
| if (filp
Hi,
Il 13/11/19 09:15, Ilie Halip ha scritto:
> The module parameter value, when specified, should be used.
> When it is not specified, you probably still want to check the
> dmi_table.
Hmm, that does not solve the problem mentioned by Valdis: if there is no
userspace daemon piloting the fan, the
> Send the BIOS disabling code only when both the dmi_table
> and the module parameter are enabled?
The module parameter value, when specified, should be used.
When it is not specified, you probably still want to check the
dmi_table.
Coincidentally, I have a Dell laptop model which might be
affec
