linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Matthew Garrett <mjg@redhat.com>, Josh Boyer <jwboyer@redhat.com>,
	Bastien Nocera <hadess@hadess.net>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@fedoraproject.org,
	Richard Hughes <richard@hughsie.com>
Subject: Re: [PATCH] HID: hid-input: default HID_BATTERY_STRENGTH to no
Date: Sun, 22 Apr 2012 10:38:57 +0200	[thread overview]
Message-ID: <CAMuHMdWEZMWrbQrf_q9fCDj4rfxuhdqW=o9857+VseJDJ-ogyA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1204181926340.16373@pobox.suse.cz>

On Wed, Apr 18, 2012 at 19:28, Jiri Kosina <jkosina@suse.cz> wrote:
> On Wed, 18 Apr 2012, Matthew Garrett wrote:
>> > Matthew suggested that additional kernel patches were required to add a
>> > scope parameter so upower could understand that the battery is powering
>> > a device and not the system.
>> >
>> > Also, when did it become OK to force-enable a new feature that is
>> > _known_ to not work properly on recent userspace?  That makes no sense
>> > to me.
>>
>> I agree. It's a great feature, but it shouldn't be default y if
>> userspace isn't ready for it yet.
>
> Fully agreed, the 'default y' part escaped my attention. I will be
> applying the patch and pushing out to Linus.
>
> I even wonder whether we shouldn't put a warning into the Kconfig entry,
> explaining the consequences of having userspace not ready for the feature.

I saw it move from HID_BATTERY_STRENGTH=y to "# HID_BATTERY_STRENGTH
is not set" in my max-all build.

As there's no help entry, and no other option selects it, HID_BATTERY_STRENGTH
cannot be set anyway in v3.4-rc4?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-04-22  8:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 14:05 [PATCH] HID: hid-input: default HID_BATTERY_STRENGTH to no Josh Boyer
2012-04-18 14:08 ` Bastien Nocera
2012-04-18 14:11   ` Josh Boyer
2012-04-18 14:24     ` Matthew Garrett
2012-04-18 17:12       ` Jeremy Fitzhardinge
2012-04-18 17:20         ` Matthew Garrett
2012-04-18 17:28       ` Jiri Kosina
2012-04-22  8:38         ` Geert Uytterhoeven [this message]
2012-04-24  8:52           ` Jiri Kosina

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='CAMuHMdWEZMWrbQrf_q9fCDj4rfxuhdqW=o9857+VseJDJ-ogyA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=hadess@hadess.net \
    --cc=jeremy@goop.org \
    --cc=jkosina@suse.cz \
    --cc=jwboyer@redhat.com \
    --cc=kernel-team@fedoraproject.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=richard@hughsie.com \
    /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;
as well as URLs for NNTP newsgroup(s).