linux-kernel - Re: [PATCH] MAINTAINERS: Remove Hans J. Koch entries

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:	Fri, 21 Jun 2013 11:15:20 +0200
From:	Michal Simek <monstr@...str.eu>
To:	"Hans J. Koch" <hjk@...sjkoch.de>
CC:	Joe Perches <joe@...ches.com>, Pavel Machek <pavel@....cz>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: [PATCH] MAINTAINERS: Remove Hans J. Koch entries

On 06/21/2013 04:50 AM, Hans J. Koch wrote:
> On Thu, Jun 20, 2013 at 09:20:27AM -0700, Joe Perches wrote:
>> On Thu, 2013-06-20 at 18:01 +0200, Pavel Machek wrote:
>>> Anyway, Hans disappeared, so Greg takes patches, again.
> 
> I wasn't able to take part in kernel development because I was heavily
> involved in hardware development project. I always thought it would be just
> a few more days, but then it became half a year. I know I should have given
> an explanation and didn't. Sorry for that.
> 
>>
>> Maybe this is appropriate then.
>>
>> Signed-off-by: Joe Perches <joe@...ches.com>
>> ---
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 69fea4f..dc9d04a 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -5253,9 +5253,8 @@ F:	Documentation/hwmon/max16065
>>  F:	drivers/hwmon/max16065.c
>>  
>>  MAX6650 HARDWARE MONITOR AND FAN CONTROLLER DRIVER
>> -M:	"Hans J. Koch" <hjk@...sjkoch.de>
>>  L:	lm-sensors@...sensors.org
>> -S:	Maintained
>> +S:	Orphan
>>  F:	Documentation/hwmon/max6650
>>  F:	drivers/hwmon/max6650.c
> 
> ACK to that one. It was never my idea to have a MAINTAINERS entry for that.
> Jean Delvare suggested it, so it came in. The MAX6650 was in a project I was
> working on 6 years ago, and I wrote the driver at that time. Meanwhile, I
> don't even have hardware with a MAX6650 anymore.
> 
> Does each little driver really need a MAINTAINERS entry? In my opinion, it
> should only be there if it is clear that it's not just a short project work.
> 
>>  
>> @@ -8795,7 +8794,6 @@ F:	fs/hostfs/
>>  F:	fs/hppfs/
>>  
>>  USERSPACE I/O (UIO)
>> -M:	"Hans J. Koch" <hjk@...sjkoch.de>
>>  M:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>>  S:	Maintained
>>  F:	Documentation/DocBook/uio-howto.tmpl
> 
> Well, you can do that if you want. But I still feel associated with UIO
> and sincerely hope I'm back again to fulfill my duties as a maintainer.

ok then can you please comment my patches?
I think it is not necessary to have one driver which support UIO without IRQ
and then second which support both cases.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



Download attachment "signature.asc" of type "application/pgp-signature" (264 bytes)