linux-kernel - Re: [PATCH, RFC] MAINTAINERS: update OSD 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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 02 May 2017 07:33:32 -0400
From:   Jeff Layton <jlayton@...hat.com>
To:     Christoph Hellwig <hch@....de>, ooo@...ctrozaur.com,
        bhalevy@...il.com
Cc:     linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
        linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH, RFC] MAINTAINERS: update OSD entries

On Tue, 2017-05-02 at 09:57 +0200, Christoph Hellwig wrote:
> The open-osd domain doesn't exist anymore, and mails to the list lead
> to really annoying bounced that repeat every day.
> 
> Also the primarydata address for Benny bounces, and while I have a new
> one for him he doesn't seem to be maintaining the OSD code any more.
> 
> Which beggs the question:  should we really leave the Supported status
> in MAINTAINERS given that the code is barely maintained?
> 
> Signed-off-by: Christoph Hellwig <hch@....de>
> ---
>  MAINTAINERS | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1bb06c5f7716..28dd83a1d9e2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9418,10 +9418,6 @@ F:	drivers/net/wireless/intersil/orinoco/
>  
>  OSD LIBRARY and FILESYSTEM
>  M:	Boaz Harrosh <ooo@...ctrozaur.com>
> -M:	Benny Halevy <bhalevy@...marydata.com>
> -L:	osd-dev@...n-osd.org
> -W:	http://open-osd.org
> -T:	git git://git.open-osd.org/open-osd.git
>  S:	Maintained
>  F:	drivers/scsi/osd/
>  F:	include/scsi/osd_*

Hah, you beat me to it! I was going to spin up a patch for this today.

Acked-by: Jeff Layton <jlayton@...hat.com>