From: Michal Simek <monstr@monstr.eu>
To: "Hans J. Koch" <hjk@hansjkoch.de>
Cc: Joe Perches <joe@perches.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [PATCH] MAINTAINERS: Remove Hans J. Koch entries
Date: Fri, 21 Jun 2013 11:15:20 +0200 [thread overview]
Message-ID: <51C419A8.3010707@monstr.eu> (raw)
In-Reply-To: <20130621025031.GG4775@local>
[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]
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@perches.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@hansjkoch.de>
>> L: lm-sensors@lm-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@hansjkoch.de>
>> M: Greg Kroah-Hartman <gregkh@linuxfoundation.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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-06-21 9:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 14:01 [RFC PATCH 1/2] uio: Use Use of_match_ptr() macro in uio_pdrv_genirq.c Michal Simek
2013-05-23 14:01 ` [RFC PATCH 2/2] uio: Add two platform uio drivers to one Michal Simek
2013-05-29 11:28 ` Michal Simek
2013-06-03 12:34 ` Michal Simek
2013-06-03 21:05 ` Greg Kroah-Hartman
2013-06-12 5:43 ` Michal Simek
2013-06-20 16:01 ` Pavel Machek
2013-06-20 16:20 ` [PATCH] MAINTAINERS: Remove Hans J. Koch entries Joe Perches
2013-06-20 16:30 ` [lm-sensors] " Guenter Roeck
2013-06-20 17:09 ` Joe Perches
2013-06-21 2:50 ` Hans J. Koch
2013-06-21 3:08 ` Joe Perches
2013-06-21 7:47 ` [lm-sensors] " Jean Delvare
2013-06-21 9:15 ` Michal Simek [this message]
2013-06-20 17:11 ` [RFC PATCH 2/2] uio: Add two platform uio drivers to one Michal Simek
2013-06-20 23:13 ` Pavel Machek
2013-06-21 9:06 ` Michal Simek
2013-06-10 8:59 ` Michal Simek
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=51C419A8.3010707@monstr.eu \
--to=monstr@monstr.eu \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=pavel@ucw.cz \
/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).