From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
drivshin.allworx@gmail.com, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pyra-handheld.com,
marek@goldelico.com, letux-kernel@openphoenux.org,
Andrey Utkin <andrey_utkin@fastmail.com>
Subject: Re: [PATCH v2 0/2] led: is31fl32xx: minor improvements
Date: Tue, 19 Jul 2016 08:59:24 +0200 [thread overview]
Message-ID: <578DCFCC.6070304@samsung.com> (raw)
In-Reply-To: <cover.1468861410.git.hns@goldelico.com>
Hi Nikolaus,
On 07/18/2016 07:03 PM, H. Nikolaus Schaller wrote:
> Changes V2:
> * added tested&acked-by David Rivshin <drivshin@allworx.com> (received off-list)
> * fixes: (received off-list)
>
> 2016-07-18 18:39:40: while developing the is31fl319x driver we found some minor issues relevant in the is31fl32xx driver.
>
> H. Nikolaus Schaller (2):
> led: is31fl32xx: fix typo in id and match table names
> led: is31fl32xx: define complete i2c_device_id table
>
> drivers/leds/leds-is31fl32xx.c | 24 +++++++++++++++---------
> 1 file changed, 15 insertions(+), 9 deletions(-)
>
Patch set applied, thanks.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2016-07-19 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 17:03 [PATCH v2 0/2] led: is31fl32xx: minor improvements H. Nikolaus Schaller
2016-07-18 17:03 ` [PATCH v2 1/2] led: is31fl32xx: fix typo in id and match table names H. Nikolaus Schaller
2016-07-18 17:03 ` [PATCH v2 2/2] led: is31fl32xx: define complete i2c_device_id table H. Nikolaus Schaller
2016-07-19 6:59 ` Jacek Anaszewski [this message]
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=578DCFCC.6070304@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=andrey_utkin@fastmail.com \
--cc=drivshin.allworx@gmail.com \
--cc=galak@codeaurora.org \
--cc=hns@goldelico.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).