From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from albert.telenet-ops.be (albert.telenet-ops.be [195.130.137.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A7E691E0DE6 for ; Mon, 21 Oct 2024 07:50:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.130.137.90 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729497007; cv=none; b=e4YYh2ADmQW/liDT8IhYjCWR1ZoBsMu89QWqJJa7nVYRrBNmqzITzEmxliyzrwjUO/a2w9XF1aot7qZAakyC9osxAT7U63TfWsBbMtvBtrE6CbJV/x0P2o5im2xJl3OKPfQdSoKxIcObjATGHzMQtHzWojhLfXK4/HaEZJdWCf0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1729497007; c=relaxed/simple; bh=MeSPUEu4aroRvWcUFbbfD3U1640yPblXHyoz9jlFJGI=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=RM9pvDSPaJTVzecvIaidGB3AHmyqpGBXMOto5ansYLt1bkiWdpnnrvW2DNshIAKUaFrI46QoYZ+nN5XsIthtz+2vE4PIq9X3//Q7ec8+tu8DSyIc1L4DLpaT6zvPzlJYjTORDgNgbajH9cVl9zIcqsEX+alADPkifbaIrY7jL2E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org; spf=none smtp.mailfrom=linux-m68k.org; arc=none smtp.client-ip=195.130.137.90 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux-m68k.org Received: from ramsan.of.borg ([IPv6:2a02:1810:ac12:ed80:3e71:ec8b:abc6:b434]) by albert.telenet-ops.be with cmsmtp id Svpx2D0023tSf9h06vpxGg; Mon, 21 Oct 2024 09:49:57 +0200 Received: from geert (helo=localhost) by ramsan.of.borg with local-esmtp (Exim 4.95) (envelope-from ) id 1t2nAq-004Eao-U2; Mon, 21 Oct 2024 09:49:56 +0200 Date: Mon, 21 Oct 2024 09:49:56 +0200 (CEST) From: Geert Uytterhoeven To: Greg Kroah-Hartman cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements. In-Reply-To: <2024101835-tiptop-blip-09ed@gregkh> Message-ID: References: <2024101835-tiptop-blip-09ed@gregkh> Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Hi Greg, Thanks for your patch, which is now commit 6e90b675cf942e50 ("MAINTAINERS: Remove some entries due to various compliance requirements.") in v6.12-rc4. On Fri, 18 Oct 2024, Greg Kroah-Hartman wrote: > Remove some entries due to various compliance requirements. They can come > back in the future if sufficient documentation is provided. This is very vague... What are "various compliance requirements"? What does "sufficient documentation" mean? I can guess, but I think it's better to spell out the rules, as Linux kernel development is done "in the open". I am also afraid this is opening the door for further (ab)use... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds