mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: lenb@kernel.org, "Michael S. Tsirkin" <mst@dev.mellanox.co.il>,
	Hugh Dickins <hugh@veritas.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ACPI: thinkpad-acpi: change thinkpad-acpi input default and kconfig help
Date: Sat, 11 Aug 2007 21:06:02 +0300	[thread overview]
Message-ID: <20070811180602.GA17843@mellanox.co.il> (raw)
In-Reply-To: <11868017143582-git-send-email-hmh@hmh.eng.br>

> Quoting Henrique de Moraes Holschuh <hmh@hmh.eng.br>:
> Subject: [PATCH 3/3] ACPI: thinkpad-acpi: change thinkpad-acpi input default and kconfig help
> 
> The current kconfig help text was misleading users.  Also, the default for
> an input-layer-optimized support caused way too many problems without
> up-to-date userspace in place.
> 
> So, rework the help text, and change the default to N.  Note that
> distributions are supposed to enable this option as soon as they update HAL
> to a version that handles the thinkpad-acpi new input layer interface.

I don't really know the details here, so I could be completely wrong.

However, generally, forcing HAL and kernel to be in sync really
looks to me like a non-ideal way to handle interface change.
For example, this would mean that one can't use the same kernel
for multiple distributions, and for a person like me
that needs to switch distros all the time, it seems like a pain.

Could not the kernel expose both new and old interfaces
somehow, so that HAL can be updated without recompiling the kernel?
For example, there could be a sysfs interface which let the HAL set
the desired interface version.

Couldn't that work?
This seems easy to code up.
Want a patch like that?

-- 
MST

       reply	other threads:[~2007-08-11 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11868017142597-git-send-email-hmh@hmh.eng.br>
     [not found] ` <11868017143582-git-send-email-hmh@hmh.eng.br>
2007-08-11 18:06   ` Michael S. Tsirkin [this message]
2007-08-11 22:16     ` Henrique de Moraes Holschuh
2007-08-16  7:30       ` Michael S. Tsirkin
2007-08-16 12:25         ` Henrique de Moraes Holschuh
2007-08-16 12:28           ` Michael S. Tsirkin
2007-08-16 13:03             ` Henrique de Moraes Holschuh

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=20070811180602.GA17843@mellanox.co.il \
    --to=mst@dev.mellanox.co.il \
    --cc=hmh@hmh.eng.br \
    --cc=hugh@veritas.com \
    --cc=lenb@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®