linux-kernel - Re: [PATCH] kvm/mips: update MAINTAINERS

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]

Message-ID: <20230620125113.GE10520@alpha.franken.de>
Date:   Tue, 20 Jun 2023 14:51:14 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Yu Zhao <yuzhao@...gle.com>
Cc:     Huacai Chen <chenhuacai@...nel.org>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Aleksandar Markovic <aleksandar.qemu.devel@...il.com>,
        linux-mips@...r.kernel.org, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kvm/mips: update MAINTAINERS

On Sat, Jun 17, 2023 at 12:53:35PM -0600, Yu Zhao wrote:
> Aleksandar Markovic was last seen in Oct 2020 [1] and cannot be
> reached for multiple days because of "Recipient inbox full".
> 
> [1] https://lore.kernel.org/all/1602103041-32017-4-git-send-email-aleksandar.qemu.devel@gmail.com/
> 
> Signed-off-by: Yu Zhao <yuzhao@...gle.com>
> ---
>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6992b7cc7095..9de60ba04b6d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11379,7 +11379,6 @@ F:	tools/testing/selftests/kvm/aarch64/
>  
>  KERNEL VIRTUAL MACHINE FOR MIPS (KVM/mips)
>  M:	Huacai Chen <chenhuacai@...nel.org>
> -M:	Aleksandar Markovic <aleksandar.qemu.devel@...il.com>
>  L:	linux-mips@...r.kernel.org
>  L:	kvm@...r.kernel.org
>  S:	Maintained
> -- 
> 2.41.0.162.gfafddb0af9-goog
> 

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]