linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.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: Tue, 7 Feb 2012 11:13:10 +0000	[thread overview]
Message-ID: <20120207111309.GB3332@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120206152307.7d1fb316@v0nbox>

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

On Mon, Feb 06, 2012 at 03:23:07PM -0500, Vivien Didelot wrote:

> 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?

It would normally be done in arch/ code.  I'm not sure if Richard will
get back to you, he's been inactive lately (working on Yocto stuff
instead).

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-07 11:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 21:05 [PATCH v5 0/5] Support for the TS-5500 platform Vivien Didelot
2012-02-01 21:05 ` [PATCH v5 1/5] x86/platform: (TS-5500) add platform base support Vivien Didelot
2012-02-01 21:05 ` [PATCH v5 2/5] x86/platform: (TS-5500) add GPIO support Vivien Didelot
2012-02-01 21:30   ` Alan Cox
2012-02-02 19:33     ` Guenter Roeck
2012-02-06 15:37       ` Mark Brown
2012-02-06 20:23         ` Vivien Didelot
2012-02-07 11:13           ` Mark Brown [this message]
2012-02-06 15:16   ` Mark Brown
2012-02-01 21:05 ` [PATCH v5 3/5] x86/platform: (TS-5500) add LED support Vivien Didelot
2012-02-01 21:05 ` [PATCH v5 4/5] hwmon: add MAX197 support Vivien Didelot
2012-02-01 21:35   ` Guenter Roeck
2012-02-06 20:15     ` Vivien Didelot
2012-02-06 20:46       ` Guenter Roeck
2012-02-10 16:07         ` Vivien Didelot
2012-02-10 16:15           ` Guenter Roeck
2012-02-10 18:14             ` Vivien Didelot
2012-02-20 18:27               ` Guenter Roeck
2012-02-20 19:56                 ` Vivien Didelot
2012-02-01 21:05 ` [PATCH v5 5/5] x86/platform: (TS-5500) add ADC support 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=20120207111309.GB3332@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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=vivien.didelot@savoirfairelinux.com \
    --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 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).