public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Laszlo Papp <lpapp@kde.org>
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>,
	hjk@hansjkoch.de, linux-kernel@vger.kernel.org,
	lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] hwmon: (max6650) Add support for gpiodef
Date: Fri, 22 Nov 2013 08:04:57 -0800	[thread overview]
Message-ID: <20131122160457.GA3951@roeck-us.net> (raw)
In-Reply-To: <CAOMwXhNx0v52BvxSWPrHFsGTvxss7N4tZT3gHMFJ8hz_HmvS5w@mail.gmail.com>

On Fri, Nov 22, 2013 at 02:50:50PM +0000, Laszlo Papp wrote:
> On Fri, Nov 22, 2013 at 2:35 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > On 11/22/2013 01:23 AM, Laszlo Papp wrote:
> >>
> >> Just to clarify: you want to have ./gpio/gpio-max6650.c?
> >>
> > No, I never said that. I wanted you to register the gpio pins
> > with the gpio subsystem. I didn't ask you to write a separate
> > driver for it.
> >
> > Sure, strictly speaking one could write a top level mfd driver
> > and separate gpio and hwmon drivers, but at least in my opinion
> > that would be overkill. I also never suggested this; you brought
> > the term mfd into the discussion.
> 
> Why is it an overkill to write a separate gpio driver for this, and
> potentially also for the gpio status register of this particular MAXIM
> chip?
> 
> Other gpio drivers in the gpio folder are also short. This would not
> become long either.
> 
No one prevents you from writing a separate gpio driver. I will certainly
not prevent you from doing it. Just don't claim that I requested it.
Same is true for an mfd driver; I won't prevent you from writing one.
But don't claim that I told you to do it.

Guenter

  reply	other threads:[~2013-11-22 16:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 14:51 [PATCH] hwmon: (max6650) Add support for gpiodef Laszlo Papp
2013-11-14 17:24 ` Guenter Roeck
     [not found]   ` <CAOMwXhNdo8aRGH9AL+JxYnDg2zAN4+-TeHJU=Kc1kDKmyYuYmA@mail.gmail.com>
2013-11-14 18:18     ` Guenter Roeck
2013-11-14 18:35       ` Laszlo Papp
2013-11-14 19:00         ` Guenter Roeck
2013-11-14 20:26           ` Laszlo Papp
     [not found]             ` <CAJ4dqQu0=HP=Ut+VnNjkSL2cE8QN+JRa-Xd8X01ij+ijKUKxwA@mail.gmail.com>
2013-11-19 16:42               ` Laszlo Papp
2013-11-19 16:54                 ` Guenter Roeck
2013-11-19 18:00                   ` [lm-sensors] " Guenter Roeck
2013-11-19 19:43                     ` Laszlo Papp
2013-11-21 15:20                       ` Laszlo Papp
2013-11-21 17:34                         ` Guenter Roeck
2013-11-21 20:52                           ` Laszlo Papp
2013-11-22  9:23                             ` Laszlo Papp
2013-11-22 14:35                               ` Guenter Roeck
2013-11-22 14:50                                 ` Laszlo Papp
2013-11-22 16:04                                   ` Guenter Roeck [this message]
2013-11-22 17:47                                     ` Laszlo Papp
2013-11-22 18:05                                       ` Guenter Roeck
2013-11-22 18:08                                         ` Laszlo Papp
2013-12-16 15:56                                           ` Laszlo Papp
2013-12-16 17:27                                             ` Guenter Roeck
2013-12-16 18:28                                               ` Laszlo Papp
2013-12-16 18:28                                                 ` Laszlo Papp
2013-12-16 19:55                                                   ` Guenter Roeck
2013-11-14 18:54 ` Laszlo Papp

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=20131122160457.GA3951@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=hjk@hansjkoch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=lpapp@kde.org \
    --cc=marcus.folkesson@gmail.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