From: "Pali Rohár" <pali.rohar@gmail.com>
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
Subject: Re: [PATCH v3] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410
Date: Mon, 13 Nov 2017 16:12:12 +0100 [thread overview]
Message-ID: <20171113151212.t2t5d7oxops7ckvc@pali> (raw)
In-Reply-To: <20171112100110.669a95d04dbb6b53be537852cb8ecb8c.107c268866.wbe@email22.secureserver.net>
On Sunday 12 November 2017 10:01:10 Gabriel M. Elder wrote:
> If necessary, I am willing to test whatever final proposed patch the
> community recommends, settles on, and accepts. Would you all like me to
> test the v3 patch as well?
v3 has just renamed variable, so I do not think that it is needed to
test it again, if you have already tested v2. But of course you can test
v3...
> Or are we calling it good at this point, and
> can expect this to be merged into a final stable kernel release sometime
> soon? I must admit, I'm looking forward to officially making this bug go
> bye-bye!
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-11-13 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 17:01 [PATCH v3] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410 Gabriel M. Elder
2017-11-13 15:12 ` Pali Rohár [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-18 18:06 [PATCH v2] " Pali Rohár
2017-11-02 20:25 ` [PATCH v3] " Pali Rohár
2017-11-03 1:18 ` Darren Hart
2017-11-11 22:12 ` Pali Rohár
2017-12-08 21:41 ` 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=20171113151212.t2t5d7oxops7ckvc@pali \
--to=pali.rohar@gmail.com \
--cc=Mario.Limonciello@dell.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gabriel@tekgnowsys.com \
--cc=gabriele.mzt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--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).