From: "Gabriel M. Elder" <gabriel@tekgnowsys.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Darren Hart" <dvhart@infradead.org>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Andy Shevchenko" <andy@infradead.org>,
"Gabriele Mazzotta" <gabriele.mzt@gmail.com>,
Mario.Limonciello@dell.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410
Date: Sat, 21 Oct 2017 10:55:03 -0700 [thread overview]
Message-ID: <20171021105503.669a95d04dbb6b53be537852cb8ecb8c.08db51c8a1.wbe@email22.secureserver.net> (raw)
-------- Original Message --------
Subject: Re: [PATCH v2] dell-laptop: Fix keyboard led max_brightness
property for Dell Latitude E6410
From: Pali Rohár <pali.rohar@gmail.com>
Date: Thu, October 19, 2017 1:31 pm
To: "Gabriel M. Elder" <gabriel@tekgnowsys.com>
Cc: Darren Hart <dvhart@infradead.org>, Matthew Garrett
<mjg59@srcf.ucam.org>, Andy Shevchenko <andy@infradead.org>, Gabriele
Mazzotta <gabriele.mzt@gmail.com>, Mario.Limonciello@dell.com,
platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
On Thursday 19 October 2017 11:20:35 Gabriel M. Elder wrote:
> I will be happy to test out whichever patch(es) present the most
> appropriate approach, as a matter of consensus.
>
> Would that be the PATCH v2
> (https://patchwork.kernel.org/patch/10015149/) that I should be testing?
Yes, v2.
--
Pali Rohár
pali.rohar@gmail.com
-------- End Original Message --------
Based on my testing, the v2 patch seems to work fine.
- Gabriel
next reply other threads:[~2017-10-21 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 17:55 Gabriel M. Elder [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-19 18:20 [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410 Gabriel M. Elder
2017-10-19 18:31 ` Pali Rohár
2017-10-15 16:03 [PATCH] " Pali Rohár
2017-10-18 18:06 ` [PATCH v2] " Pali Rohár
2017-10-18 19:09 ` Andy Shevchenko
2017-10-18 19:14 ` Pali Rohár
2017-10-18 20:00 ` Darren Hart
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=20171021105503.669a95d04dbb6b53be537852cb8ecb8c.08db51c8a1.wbe@email22.secureserver.net \
--to=gabriel@tekgnowsys.com \
--cc=Mario.Limonciello@dell.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gabriele.mzt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.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).