From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"x86@kernel.org" <x86@kernel.org>,
Jerome Oufella <jerome.oufella@savoirfairelinux.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
Jean Delvare <khali@linux-fr.org>,
Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [lm-sensors] [PATCH v5 2/5] x86/platform: (TS-5500) add GPIO support
Date: Mon, 06 Feb 2012 20:23:07 +0000 [thread overview]
Message-ID: <20120206152307.7d1fb316@v0nbox> (raw)
In-Reply-To: <20120206153742.GE10173@sirena.org.uk>
Le Mon, 6 Feb 2012 15:37:42 +0000,
Mark Brown <broonie@opensource.wolfsonmicro.com> a écrit :
> On Thu, Feb 02, 2012 at 11:33:56AM -0800, Guenter Roeck wrote:
> > On Wed, 2012-02-01 at 16:30 -0500, Alan Cox wrote:
>
> > > > My first RFC patches set has every driver separated. As they are
> > > > really specific to the platform, people seem to agree with
> > > > grouping them, mainly because they won't be shared. I changed
> > > > that in the following patches sets, and X86 maintainers seemed
> > > > to be ok with that.
>
> > It looks like things are going back and forth a bit. If I were
> > Vivien, I would be a bit frustrated by now and be close to giving
> > up (Vivien, I really commend you for your patience).
>
> OTOH I just looked back and saw that some of the review comments I
> just made were also made against the first version of this driver I
> noticed (v2) but appear to have been ignored, the request tracking
> stands out.
>
> > Is there a written guideline or policy people can look and point to
> > if/when something like this comes up ? Otherwise we may have the
> > LED/GPIO/xxx maintainers point one way, the X86 maintainers point
> > the other way, and thus may have reached a complete deadlock.
>
> I'm not sure I'm seeing much conflict here TBH, looking at the above
> and the history I have to hand I'd say it's reading like the x86
> maintainers aren't fussed either way and the people doing kernel wide
> work on things like this prefer getting stuff integrated into the
> frameworks.
Thanks for the comments. I'll then move the GPIO driver back to
drivers/gpio and fix what Mark pointed out.
I Cc Richard Purdie, to have his maintainer view on the platform LED
declaration. Is it ok in the ts5500_led.c platform file, or should it
better be moved into drivers/leds/leds-ts5500.c, or maybe directly
declared in the main ts5500.c platform code?
Thanks,
Vivien.
--
Vivien Didelot
Savoir-faire Linux Inc.
Tel: (514) 276-5468 #149
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"x86@kernel.org" <x86@kernel.org>,
Jerome Oufella <jerome.oufella@savoirfairelinux.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
Jean Delvare <khali@linux-fr.org>,
Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [PATCH v5 2/5] x86/platform: (TS-5500) add GPIO support
Date: Mon, 6 Feb 2012 15:23:07 -0500 [thread overview]
Message-ID: <20120206152307.7d1fb316@v0nbox> (raw)
In-Reply-To: <20120206153742.GE10173@sirena.org.uk>
Le Mon, 6 Feb 2012 15:37:42 +0000,
Mark Brown <broonie@opensource.wolfsonmicro.com> a écrit :
> On Thu, Feb 02, 2012 at 11:33:56AM -0800, Guenter Roeck wrote:
> > On Wed, 2012-02-01 at 16:30 -0500, Alan Cox wrote:
>
> > > > My first RFC patches set has every driver separated. As they are
> > > > really specific to the platform, people seem to agree with
> > > > grouping them, mainly because they won't be shared. I changed
> > > > that in the following patches sets, and X86 maintainers seemed
> > > > to be ok with that.
>
> > It looks like things are going back and forth a bit. If I were
> > Vivien, I would be a bit frustrated by now and be close to giving
> > up (Vivien, I really commend you for your patience).
>
> OTOH I just looked back and saw that some of the review comments I
> just made were also made against the first version of this driver I
> noticed (v2) but appear to have been ignored, the request tracking
> stands out.
>
> > Is there a written guideline or policy people can look and point to
> > if/when something like this comes up ? Otherwise we may have the
> > LED/GPIO/xxx maintainers point one way, the X86 maintainers point
> > the other way, and thus may have reached a complete deadlock.
>
> I'm not sure I'm seeing much conflict here TBH, looking at the above
> and the history I have to hand I'd say it's reading like the x86
> maintainers aren't fussed either way and the people doing kernel wide
> work on things like this prefer getting stuff integrated into the
> frameworks.
Thanks for the comments. I'll then move the GPIO driver back to
drivers/gpio and fix what Mark pointed out.
I Cc Richard Purdie, to have his maintainer view on the platform LED
declaration. Is it ok in the ts5500_led.c platform file, or should it
better be moved into drivers/leds/leds-ts5500.c, or maybe directly
declared in the main ts5500.c platform code?
Thanks,
Vivien.
--
Vivien Didelot
Savoir-faire Linux Inc.
Tel: (514) 276-5468 #149
next prev parent reply other threads:[~2012-02-06 20:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 21:05 [lm-sensors] [PATCH v5 0/5] Support for the TS-5500 platform Vivien Didelot
2012-02-01 21:05 ` Vivien Didelot
2012-02-01 21:05 ` [lm-sensors] [PATCH v5 1/5] x86/platform: (TS-5500) add platform base support Vivien Didelot
2012-02-01 21:05 ` Vivien Didelot
2012-02-01 21:05 ` [lm-sensors] [PATCH v5 2/5] x86/platform: (TS-5500) add GPIO support Vivien Didelot
2012-02-01 21:05 ` Vivien Didelot
2012-02-01 21:30 ` [lm-sensors] " Alan Cox
2012-02-01 21:30 ` Alan Cox
2012-02-02 19:33 ` [lm-sensors] " Guenter Roeck
2012-02-02 19:33 ` Guenter Roeck
2012-02-06 15:37 ` [lm-sensors] " Mark Brown
2012-02-06 15:37 ` Mark Brown
2012-02-06 20:23 ` Vivien Didelot [this message]
2012-02-06 20:23 ` Vivien Didelot
2012-02-07 11:13 ` [lm-sensors] " Mark Brown
2012-02-07 11:13 ` Mark Brown
2012-02-06 15:16 ` [lm-sensors] " Mark Brown
2012-02-06 15:16 ` Mark Brown
2012-02-01 21:05 ` [lm-sensors] [PATCH v5 3/5] x86/platform: (TS-5500) add LED support Vivien Didelot
2012-02-01 21:05 ` Vivien Didelot
2012-02-01 21:05 ` [lm-sensors] [PATCH v5 4/5] hwmon: add MAX197 support Vivien Didelot
2012-02-01 21:05 ` Vivien Didelot
2012-02-01 21:35 ` [lm-sensors] " Guenter Roeck
2012-02-01 21:35 ` Guenter Roeck
2012-02-06 20:15 ` [lm-sensors] " Vivien Didelot
2012-02-06 20:15 ` Vivien Didelot
2012-02-06 20:46 ` [lm-sensors] " Guenter Roeck
2012-02-06 20:46 ` Guenter Roeck
2012-02-10 16:07 ` [lm-sensors] " Vivien Didelot
2012-02-10 16:07 ` Vivien Didelot
2012-02-10 16:15 ` [lm-sensors] " Guenter Roeck
2012-02-10 16:15 ` Guenter Roeck
2012-02-10 18:14 ` [lm-sensors] " Vivien Didelot
2012-02-10 18:14 ` Vivien Didelot
2012-02-20 18:27 ` [lm-sensors] " Guenter Roeck
2012-02-20 18:27 ` Guenter Roeck
2012-02-20 19:56 ` [lm-sensors] " Vivien Didelot
2012-02-20 19:56 ` Vivien Didelot
2012-02-01 21:05 ` [lm-sensors] [PATCH v5 5/5] x86/platform: (TS-5500) add ADC support Vivien Didelot
2012-02-01 21:05 ` Vivien Didelot
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=20120206152307.7d1fb316@v0nbox \
--to=vivien.didelot@savoirfairelinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=guenter.roeck@ericsson.com \
--cc=hpa@zytor.com \
--cc=jerome.oufella@savoirfairelinux.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mingo@redhat.com \
--cc=rpurdie@rpsys.net \
--cc=tglx@linutronix.de \
--cc=x86@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.