From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH v7 0/8] efi/firmware/platform-x86: Add EFI embedded fw support Date: Tue, 8 Oct 2019 13:05:12 +0200 Message-ID: <20191008110512.GA116541@gmail.com> References: <20191004145056.43267-1-hdegoede@redhat.com> <20191007141956.GA25347@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Hans de Goede Cc: Ard Biesheuvel , Darren Hart , Andy Shevchenko , Luis Chamberlain , Greg Kroah-Hartman , "Rafael J . Wysocki" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , Jonathan Corbet , Dmitry Torokhov , Peter Jones , Dave Olsthoorn , x86@kernel.org, platform-driver-x86@vger.kernel.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-input@vger.kernel.org List-Id: linux-input@vger.kernel.org * Hans de Goede wrote: > > So I was looking for a high level 0/ boilerplate description of this > > series, to explain what "EFI embedded fw" is, what problems it solves and > > how it helps the kernel in general - and found this in 2/8: > > Sorry you had to dig into the individual patch changelogs for that > I sorta assumed that everyone involved would still vaguely remember > what this series is about. Wasn't *that* hard to do and I intended to read the patches anyway. ;-) Thanks for the explanation and the answers, this all looks good to me in principle and in implementation as well. Thanks, Ingo 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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FSL_HELO_FAKE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 059AAC4360C for ; Tue, 8 Oct 2019 11:05:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D3FE7217D7 for ; Tue, 8 Oct 2019 11:05:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570532720; bh=t8CmXG9crxwkqdt9gjxcL8E0dO3BQSoadiR9vcrhQFc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=vX6elGQfFi3+NBZHJWSRbP5RZaql6WWyOLax6yubZIQhOpq7Mn7QwUJaguGV0mR7j mDHtqr9HKz5Pz0qdhZxDNtQZjYeE2q4Dlemu2L9fTcdF2HYcIA1cnykQMENHQm+8Y/ OCgl0riE2qa7cRTmJjnXUTVAbqeeYsgip4C8VHuk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730256AbfJHLFU (ORCPT ); Tue, 8 Oct 2019 07:05:20 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:35491 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730118AbfJHLFU (ORCPT ); Tue, 8 Oct 2019 07:05:20 -0400 Received: by mail-wr1-f66.google.com with SMTP id v8so18902678wrt.2; Tue, 08 Oct 2019 04:05:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=J92IWr2VJrY20cgBoCqlCjKaHqq8B9mSOS3pdXzLByg=; b=GKdJOsXaS7oy+vYxeRfBem2DpcZoE6xluLj7B3VZTd++gIRdIJHAcBwflVR9iSzhQz 4agGD+SXLAQpDauw+zsmyJmc6rRgnr9DExjP2T7luIcMToCWeoU58bsgQvtMzaxWkRY4 Yh7pen97p38z77CKnPJnh2YPRXmecSZDn5dNy5gVegEQUeHiEj3ILmYDYCH6lP0lPMQV Uxxiy9i6L7xJ5CBeziZ8AkQTnSX7D72++VNm0FsKLTLNQggABvslqBOxcNTTzly3Mcwm tQjQvDNBWsHZxyvcN5Git1HIfvbXLuuPnSinhKmCgnUGTiymalAPRNBzrtya3eV4Ko/d Z0JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=J92IWr2VJrY20cgBoCqlCjKaHqq8B9mSOS3pdXzLByg=; b=eRoiECqRaY3kYbXNEVkLVYA04ewDU7GuVsekHS0xalFyvae5nfNIws1ybPtN34IDSA mAayZ81e//su919o5JjDuurfOfaCRz+aBKddvJGpnr97QLo6aLsFuJRkP8ExOHWSeOWq kCyu44u1CbFpL5REJ7hOgS9+Zd4r9CKQQtvqNRwSIPc0mHLD3bnbsgMCa6wUGr8ZJ3Uz fIUYgjWZ/fKm33gwBR56iqmm/DPvQgv3EnOdgkDuQ1cCzc7qeCRbzFO27ScP8JNoITCS P+KPVlc8jICTGwe/kRFomRLu1ERS8cURWKOY26mAw0jNV0zQwgm9sSh/yrmp0lSUda7+ DqNw== X-Gm-Message-State: APjAAAWm5M3/MTiph7ZBQH9FYYwKsHxoNbsrgBrYMypyWn4lthLYrDxt r7tnZEV4Ipcp6xQ1VW9/puQ= X-Google-Smtp-Source: APXvYqw0NawJTWZiuMShXAIsYRAaf5X0VI1pfia9S89FIVn+31OYEpLhXWLX+LczhmPApHBFq4cRVw== X-Received: by 2002:a5d:4102:: with SMTP id l2mr27721246wrp.348.1570532715866; Tue, 08 Oct 2019 04:05:15 -0700 (PDT) Received: from gmail.com (2E8B0CD5.catv.pool.telekom.hu. [46.139.12.213]) by smtp.gmail.com with ESMTPSA id e15sm21826909wrt.94.2019.10.08.04.05.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 08 Oct 2019 04:05:15 -0700 (PDT) Date: Tue, 8 Oct 2019 13:05:12 +0200 From: Ingo Molnar To: Hans de Goede Cc: Ard Biesheuvel , Darren Hart , Andy Shevchenko , Luis Chamberlain , Greg Kroah-Hartman , "Rafael J . Wysocki" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , Jonathan Corbet , Dmitry Torokhov , Peter Jones , Dave Olsthoorn , x86@kernel.org, platform-driver-x86@vger.kernel.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-input@vger.kernel.org Subject: Re: [PATCH v7 0/8] efi/firmware/platform-x86: Add EFI embedded fw support Message-ID: <20191008110512.GA116541@gmail.com> References: <20191004145056.43267-1-hdegoede@redhat.com> <20191007141956.GA25347@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-input-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org Message-ID: <20191008110512.wvuUQoZoR3NGKCdC18V48_ke3EY5xlbmG-W0-e4wH4Q@z> * Hans de Goede wrote: > > So I was looking for a high level 0/ boilerplate description of this > > series, to explain what "EFI embedded fw" is, what problems it solves and > > how it helps the kernel in general - and found this in 2/8: > > Sorry you had to dig into the individual patch changelogs for that > I sorta assumed that everyone involved would still vaguely remember > what this series is about. Wasn't *that* hard to do and I intended to read the patches anyway. ;-) Thanks for the explanation and the answers, this all looks good to me in principle and in implementation as well. Thanks, Ingo