From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: vadimp@mellanox.com, rpurdie@rpsys.net
Cc: dave@treblig.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, jiri@resnulli.us,
michaelsh@mellanox.com
Subject: Re: [patch v4] leds: add driver for Mellanox systems LEDs
Date: Thu, 08 Sep 2016 12:24:00 +0200 [thread overview]
Message-ID: <3fd4a32a-ea79-315a-486f-2dab6aa384d8@samsung.com> (raw)
In-Reply-To: <f1343a15-3553-023f-c492-6364ec79decb@samsung.com>
On 09/08/2016 12:20 PM, Jacek Anaszewski wrote:
> On 09/08/2016 09:25 AM, vadimp@mellanox.com wrote:
>> From: Vadim Pasternak <vadimp@mellanox.com>
>
>> diff --git a/Documentation/leds/leds-mlxcpld.txt
>> b/Documentation/leds/leds-mlxcpld.txt
>> new file mode 100644
>> index 0000000..7b4c2a3
>> --- /dev/null
>> +++ b/Documentation/leds/leds-mlxcpld.txt
>> @@ -0,0 +1,110 @@
>> +ver LEDs-mlxcpld
>
> I noticed this only now - is it a stray line or you intended it was
> something more meaningful?
OK, I changed it to:
Kernel driver for Mellanox systems LEDs
=======================================
followed by an empty line.
>> +==========================
>> +Driver for Mellanox systems LEDs.
>> +Provide system LED support for the nex Mellanox systems:
>> +"msx6710", "msx6720", "msb7700", "msn2700", "msx1410",
>> +"msn2410", "msb7800", "msn2740", "msn2100".
>
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-09-08 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 7:25 [patch v4] leds: add driver for Mellanox systems LEDs vadimp
2016-09-08 7:41 ` Jacek Anaszewski
2016-09-08 7:45 ` Vadim Pasternak
2016-09-08 10:20 ` Jacek Anaszewski
2016-09-08 10:20 ` Jacek Anaszewski
2016-09-08 10:24 ` Jacek Anaszewski [this message]
2016-09-08 10:39 ` Vadim Pasternak
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=3fd4a32a-ea79-315a-486f-2dab6aa384d8@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=dave@treblig.org \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--cc=rpurdie@rpsys.net \
--cc=vadimp@mellanox.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;
as well as URLs for NNTP newsgroup(s).