lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 7 Apr 2015 21:03:28 -0700
From:	Darren Hart <dvhart@...radead.org>
To:	Pali Rohár <pali.rohar@...il.com>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: Add me on list of Dell laptop drivers

On Sun, Apr 05, 2015 at 11:11:49PM +0200, Pali Rohár wrote:
> On Thursday 02 April 2015 07:10:27 Darren Hart wrote:
> > On Sun, Mar 29, 2015 at 03:38:50PM +0200, Pali Rohár wrote:
> > 
> > Please include why. No empty commit messages please.
> > 
> > For example, you've written nearly a third of the dell-wmi.c
> > driver, and all the dell-smo8800.c driver.
> > 
> 
> Ok. If you need description include this:
> 
> ===
> MAINTAINERS: Add me on list of Dell laptop drivers
> 
> I have written more parts of dell laptop drivers dell-laptop.c, 
> dell-wmi.c and dell-smo8800.c
> ===
> 
> > Dell Laptop is still pending the keyboard backlight patches
> > though I believe (have I missed them?), so you don't
> > currently have code ownership there. I agree you should be on
> > the MAINTAINERS list, but it would be good to get your
> > keyboard backlight changes in first.
> > 
> 
> ok.
> 
> > Gosh... sure seems like we should have merged that already...
> > am I missing something? The last thing I see in master,
> > testing, and next is the revert from Jan 21....
> > 
> 
> backlight support was merged for 3.19, but has small problem with 
> ALS settings. And then you decided to revert it for 3.19. After 
> that problem was fixed and last (2015-03-06) you wrote that you 
> queued patch again for 4.1 release.

Right you are, and I appear to have dropped that ball. Found it, and it's now in
my testing branch, and will run through the 0day testing, then into my next
tomorrow, still on track for 4.1.

> 
> > Also, Matthew, you're the listed maintainer for these, do you
> > agree to adding Pali?

I'm accepted silence as acceptance :-)

-- 
Darren Hart
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ