public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Paul Parsons <lost.distance@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: Add ASIC3 LED support
Date: Tue, 3 May 2011 10:33:40 +0200	[thread overview]
Message-ID: <20110503083339.GK8222@sortiz-mobl> (raw)
In-Reply-To: <325376.71935.qm@web29015.mail.ird.yahoo.com>

Hi Paul,

On Mon, May 02, 2011 at 11:16:23PM +0100, Paul Parsons wrote:
> Hi Samuel,
> 
> --- On Mon, 2/5/11, Samuel Ortiz <sameo@linux.intel.com> wrote:
> > Where is the LED driver ?
> It was posted separately - [PATCH 2/2] leds: Add ASIC3 LED support - since drivers/mfd and drivers/leds are maintained separately. Sorry, I should have cross copied them.
> 
I believe the LED driver is dependent on the asic3.h changes this patches
carry. So both patches should go in at the same time, probably through my
tree. 


> > > -static int asic3_clk_enable(struct asic3 *asic,
> > struct asic3_clk *clk)
> > > +static void asic3_clk_enable(struct asic3 *asic,
> > struct asic3_clk *clk)
> > Although a valid change, this is unrelated to this patch.
> Not completely unrelated; I call asic3_clk_enable() and found it simpler to remove the unnecessary return value rather than check it.
> 
I understood that. And I am fine with the change, but I would like it to be a
separate patch.


> > > +    asic->gpio.label = "asic3";
> > Ditto.
> Agreed; that was left in by mistake.
> 
> Should I resubmit?
Yes, please. Also, I'm deprecating the mfd_data usage in my mfd-2.6 tree, so
you should fix your code according to that.

Thanks in advance.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2011-05-03  8:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30 17:59 [PATCH 1/2] mfd: Add ASIC3 LED support Paul Parsons
2011-05-02 15:39 ` Samuel Ortiz
2011-05-02 22:16   ` Paul Parsons
2011-05-03  8:33     ` Samuel Ortiz [this message]
2011-05-03 10:41 ` Philipp Zabel
2011-05-03 10:46   ` Philipp Zabel
2011-05-03 15:38     ` Paul Parsons
2011-05-03 19:46   ` Paul Parsons

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=20110503083339.GK8222@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lost.distance@yahoo.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