Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp3210764pxm; Mon, 28 Feb 2022 14:36:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJxxCMULyPiV+Mn9GGEAE/lDVlnQfRiXb0wlDvkrdQqWkTOecWPGpq9JJopBGbHpoZ0eKoAE X-Received: by 2002:a05:6a00:21c6:b0:49f:dcb7:2bf2 with SMTP id t6-20020a056a0021c600b0049fdcb72bf2mr23828353pfj.19.1646087763468; Mon, 28 Feb 2022 14:36:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646087763; cv=none; d=google.com; s=arc-20160816; b=AaSRUCA2St3Bb6/cVn0AuPKUdvJXxK/3HJ8UJ3ifnf3V5DMh6W1i6lsJBJYVch5nhx mPF8Wcv1GUIWVjedZO+T8O1JkpwB1fxY7nkWoSrwfEfC/iKR3FWOOyDcsTyYiS1gFzKm 7vbpje00fQ+NlLqUPLZxrLZDP+fb9el3OE8LcpkBUS3OhZiAqEU4h0yy8Fj9Tv1cxhnh Rri7bUPmv9pDdB0dLRMMAzo2VgBhhhDPg2B0J4Rax+7SuKw8ekkpc/OT0iZTs7DGCFLn k/5v/6Mp1xM54spbRb3IgARO0VKzxWLP/iRC5tTUugu5Pmlep0m+u7jf4JtIVyGjjtsv Nc7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=0gYo+w+F9Yr9jXeKd4yhlIselJQUhTYBVZBr6ICmc44=; b=i1bGggcrZbRtMbX4nrEM9jIb0+q7pyx1rSaxT66W6SQ91IRoMVVWJ6uhHPw6Z+Sw/e EdupaYJQJzlcWuu+Qcor7tkpIPYd2lIYonAzQTQKT77PjBuU0JX6URSMlUbE0SOo3BqZ zlPbPJophCM4uwex7PmJHZCvfDNRnL4YwYxGfmJwxCVQ3CH59vsaN2eQ8uBUWbY62sqn +ZdP0XhZc5DOyiKRn4rAK+CMPtyKgAdDuDYLqAoeH9f0+aBUXwj602dxTQLJ5PytNWEz WS1urWWFH9XXS5XEgW9Qegy7Y0XJ5E3H8nenIPfMiD2S/bgUAHw4n9C5X06cHzASxy+i aGMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=Ih5F4FRE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f20-20020a056a001ad400b004f11edaa589si11606782pfv.227.2022.02.28.14.35.47; Mon, 28 Feb 2022 14:36:03 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=Ih5F4FRE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231232AbiB1Vzg (ORCPT + 99 others); Mon, 28 Feb 2022 16:55:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52674 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbiB1Vzf (ORCPT ); Mon, 28 Feb 2022 16:55:35 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3138426550; Mon, 28 Feb 2022 13:54:55 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 85BBD61216; Mon, 28 Feb 2022 21:54:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 561F0C340F2; Mon, 28 Feb 2022 21:54:54 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="Ih5F4FRE" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1646085292; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0gYo+w+F9Yr9jXeKd4yhlIselJQUhTYBVZBr6ICmc44=; b=Ih5F4FREcrCYLk5lw1LYw/3HpDY//WblCvSVj3bAxTYy1u8mnNT+u+M65gLh33zQ3fjbIc q9YZW/dRNDs269fTyRUxqE+Qs9nx1eI100D28JGZLhSwxO8lGoTNswdnsYjHBDvvhplE5q GQ+0usGDCbQ/ovrAkyMhAlFlgukzzVc= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 41a9ebdc (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Mon, 28 Feb 2022 21:54:52 +0000 (UTC) Received: by mail-yb1-f179.google.com with SMTP id b35so23321533ybi.13; Mon, 28 Feb 2022 13:54:51 -0800 (PST) X-Gm-Message-State: AOAM531gJa5iOwiBkPn12oMb/hEclDlJ0FKFPMQNuzh4ERvGhRWU6WYG VoNp/lbD3iJ5vEh1uaRrFEWM42xZY9HCywAWnVo= X-Received: by 2002:a25:b905:0:b0:61e:23e4:949f with SMTP id x5-20020a25b905000000b0061e23e4949fmr21728876ybj.373.1646085290051; Mon, 28 Feb 2022 13:54:50 -0800 (PST) MIME-Version: 1.0 References: <20220228183355.9090-1-Jason@zx2c4.com> In-Reply-To: From: "Jason A. Donenfeld" Date: Mon, 28 Feb 2022 22:54:39 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 2/3 v6] ACPI: allow longer device IDs To: Andy Shevchenko Cc: Ard Biesheuvel , "Rafael J. Wysocki" , Linux Kernel Mailing List , linux-crypto , ACPI Devel Maling List , Alexander Graf , Mika Westerberg , Hans de Goede , Len Brown , Greg Kroah-Hartman Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andy, On Mon, Feb 28, 2022 at 10:28 PM Andy Shevchenko wrote: > My point is that this is clear abuse of the spec and: > 1) we have to enable the broken, because it is already in the wild with > the comment that this is an issue > > AND > > 2) issue an ECR / work with MS to make sure they understand the problem. > > This can be done in parallel. What I meant as a prerequisite is to start doing > 2) while we have 1) on table. Oh, okay, that makes sense. If you want to get (2) going, by all means go for it. I have no idea how to do this myself; Ard said something about joining the UEFI forum as an individual something or another but I don't think I'm the man for the job there. Is this something that Intel can do with their existing membership (is that the right term?) at the UEFI forum? Or maybe a Microsoft engineer on the list? From my side, regarding (1), I'm basically just waiting for Rafael's "Acked-by" (or an explicit nack) so I can put this in my tree and move on. Jason