Linux LED subsystem development
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@aj.id.au>
To: "Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	linux-leds@vger.kernel.org
Cc: Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] leds: pca955x: check for I2C errors
Date: Thu, 31 Aug 2017 09:34:02 +0930	[thread overview]
Message-ID: <1504137842.5933.24.camel@aj.id.au> (raw)
In-Reply-To: <f171c638-4190-30ba-94dc-36fdf9ed10de@gmail.com>

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

On Wed, 2017-08-30 at 22:00 +0200, Jacek Anaszewski wrote:
> Hi Cedric,
> 
> Thanks for the patch.
> 
> On 08/30/2017 01:25 PM, Cédric Le Goater wrote:
> > This should also allow probing to fail when a pca955x chip is not
> > found on a I2C bus.
> > 
> > > > Signed-off-by: Cédric Le Goater <clg@kaod.org>
> > ---
> > 
> >  Andrew,
> > 
> >  The patch conflicts with your patch :
> > 
> >    "leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()"
> > 
> >  and I have chosen to be in sync with the 'for-next' branch of the
> >  linux-leds git repo. Depending on the reviews we will have to respin
> >  one or the other.
> 
> Applied yours as first.
> 

No worries, I'll resend.

Cheers,

Andrew

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2017-08-31  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 11:25 [PATCH] leds: pca955x: check for I2C errors Cédric Le Goater
2017-08-30 20:00 ` Jacek Anaszewski
2017-08-31  0:04   ` Andrew Jeffery [this message]
2017-08-31 20:23     ` Jacek Anaszewski

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=1504137842.5933.24.camel@aj.id.au \
    --to=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.net \
    /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