From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4B125C433EF for ; Mon, 11 Oct 2021 07:51:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2A72660EC0 for ; Mon, 11 Oct 2021 07:51:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234672AbhJKHxe (ORCPT ); Mon, 11 Oct 2021 03:53:34 -0400 Received: from verein.lst.de ([213.95.11.211]:36227 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234657AbhJKHx1 (ORCPT ); Mon, 11 Oct 2021 03:53:27 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B7E5968AFE; Mon, 11 Oct 2021 09:51:25 +0200 (CEST) Date: Mon, 11 Oct 2021 09:51:25 +0200 From: Christoph Hellwig To: Simon Ser Cc: Christoph Hellwig , Alex Deucher , Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List , Daniel Vetter Subject: Re: linux-next: build failure after merge of the amdgpu tree Message-ID: <20211011075125.GA11098@lst.de> References: <20211008113116.4bdd7b6c@canb.auug.org.au> <20211008192910.600a188d@canb.auug.org.au> <_POw9ikafXoqSFqiOb8SZb_uvRZ4okgD4qrl4EtJ0UBiQTV7pwV3pJIM20eIzmpuFWDeBF9NPD00r72ttX0mZZ0bNeH_J44MoaB-jfjrQSU=@emersion.fr> <20211011073348.GA10672@lst.de> <-6WWj2RSqFheia8o3VKtAiF3bELME9376cYzwiLSY1-E7p9nqfWNqJ5i86Q--BKXa3aolokj8g8nj2tQorzn0LXuD85tD_rXSfE5t1lsvBs=@emersion.fr> <20211011074316.GA10882@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Mon, Oct 11, 2021 at 07:49:44AM +0000, Simon Ser wrote: > Have you heard about the kernel no-regression rule? Here, we can't enable a new > feature because that would regress user-space which mis-uses the kernel uAPI. Then you can't enable the feature without an explicit opt-in from userspace. This ain't rocket science. > If your reply wasn't aggressive, I don't know what it is. If there is one thing I find agressive it is your extreme passive aggressive behavior.