All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH v2 2/2] hwmon: (w83l786ng) Convert to devm_hwmon_device_register_with_groups
Date: Wed, 25 Jun 2014 06:08:33 +0000	[thread overview]
Message-ID: <53AA6761.3030300@roeck-us.net> (raw)
In-Reply-To: <1403660391.31123.2.camel@phoenix>

On 06/24/2014 10:57 PM, Jean Delvare wrote:
> Hi Guenter,
>
> On Tue, 24 Jun 2014 19:24:32 -0700, Guenter Roeck wrote:
>> On a side note, it appears the chip is long since obsolete, so I wonder
>> if anyone is still using it.
>
> It wasn't very popular back then either, so odds are indeed that the
> current user count is close to 0. However this isn't the only driver in
> that case, and I know of no policy to drop drivers just because of
> this. Being able to run on old hardware is a Linux feature.
>
> I think it only makes sense to drop drivers which have been heavily
> broken for a long time without nobody complaining, or which would
> require a major rework nobody is able to spend time on.
>

Agreed.

There was a discussion about deprecating old drivers a couple
of weeks ago on the kernel summit mailing list, but I don't think
people agreed on anything. Personally I am fine with keeping drivers
in the code base.

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2014-06-25  6:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  1:39 [lm-sensors] [PATCH v2 2/2] hwmon: (w83l786ng) Convert to devm_hwmon_device_register_with_groups Axel Lin
2014-06-25  2:03 ` Kevin Lo
2014-06-25  2:24 ` Guenter Roeck
2014-06-25  5:57 ` Jean Delvare
2014-06-25  6:08 ` Guenter Roeck [this message]

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=53AA6761.3030300@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@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.