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=-13.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=ham 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 7059CC4338F for ; Wed, 28 Jul 2021 14:56:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5518360F91 for ; Wed, 28 Jul 2021 14:56:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236837AbhG1O4i (ORCPT ); Wed, 28 Jul 2021 10:56:38 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:21596 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237350AbhG1O4X (ORCPT ); Wed, 28 Jul 2021 10:56:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1627484181; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=it5Te9P2fE9hEACV7bmI0ZQUC4eOMZ6L7HHf6MGR5Mo=; b=gqvKyC+oxaz04/LupRrVhApxsAbNgvSUJrWeGJC4ogPu16glJkj9wAr9H2Gnh7brvC5MIV aeX6zn23o+v4t9/5ecRKiaNInBbUQKwdXBOvnVrDzlX7IR+8u+wHLIajIC8AHXkKuyQKSx YntlWJhdU5QrhqNWLKFoIxgk6YF9hf0= Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-98-oRDZiJBLOnStF4CgFebdKQ-1; Wed, 28 Jul 2021 10:56:20 -0400 X-MC-Unique: oRDZiJBLOnStF4CgFebdKQ-1 Received: by mail-qk1-f200.google.com with SMTP id x2-20020a05620a0ec2b02903b8bd8b612eso1742617qkm.19 for ; Wed, 28 Jul 2021 07:56:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=it5Te9P2fE9hEACV7bmI0ZQUC4eOMZ6L7HHf6MGR5Mo=; b=knaZU80K2+w9uDqAR0l7cHQf2fApYhOmwNTseUNVahkCMd6cDWw9TLf29xHokKXat1 H2Frmzy7WYIf65i08vI+sKgckbx/UrRXhaFEkqlTSesyto2OzFKNNSmolOFLa61/qlQ3 NMbJKxAWNHXYuvrpo1G61W7ep6YTomG8GFvpihZ6mPrnIzllJAbk5y5xNempUc+/pfPH XWdB9UitCg92ob2iZtpkA44tLiSlX4vuNSA1IYWHINOjbYezKJFaOxIxqos7DA47xazL 7tek19SjADtL853PT8skS9pwBOPTOlcEZct2n9W8WNmF1ooTtNXPBKe+8dK0xIgP7VgX DyyA== X-Gm-Message-State: AOAM532Gk6kimkkWxMwI7SDT2xfRfmkobmZUP74IfqEp+/jrBiWcwmob 9VDvqCG+zC3WMGnNlZETUK0BBzkPyQj8nXVft4pTR3PIjbAgpxFWVrSSoCQUJXLwOMq2gQ+FbX1 423Ktkc/XR4wUMBG09NvAqA== X-Received: by 2002:a05:622a:104b:: with SMTP id f11mr23864112qte.134.1627484179605; Wed, 28 Jul 2021 07:56:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx7m6DREgWBE6Hlfac89TKVr/iCoUvG1oqWqS55n/ROdB1Bdnlx4nra3hys5EdZ7ULEdaF4Dw== X-Received: by 2002:a05:622a:104b:: with SMTP id f11mr23864096qte.134.1627484179449; Wed, 28 Jul 2021 07:56:19 -0700 (PDT) Received: from localhost.localdomain (075-142-250-213.res.spectrum.com. [75.142.250.213]) by smtp.gmail.com with ESMTPSA id s81sm104241qka.82.2021.07.28.07.56.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 28 Jul 2021 07:56:19 -0700 (PDT) Subject: Re: [PATCH v13 0/4] Intel MAX10 BMC Secure Update Driver To: Russ Weight , mdf@kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org, "Wu, Hao" Cc: lgoncalv@redhat.com, yilun.xu@intel.com, matthew.gerlach@intel.com, richard.gong@intel.com References: <20210727225859.153572-1-russell.h.weight@intel.com> From: Tom Rix Message-ID: <65ed311d-a492-413e-33a8-f64e9c41e7c2@redhat.com> Date: Wed, 28 Jul 2021 07:56:16 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210727225859.153572-1-russell.h.weight@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-fpga@vger.kernel.org Russ > Russ Weight (4): > fpga: m10bmc-sec: create max10 bmc secure update driver > fpga: m10bmc-sec: expose max10 flash update count > fpga: m10bmc-sec: expose max10 canceled keys in sysfs Since sec-mgr is taking a long time, I am looking at splitting out parts we can agree on. These 3 patches are a new dfl specific driver and do not depend on sec-mgr. Here is a poc on char-misc-next, splitting them and moving them before sec-mgr https://github.com/trixirt/linux-next/commits/sec-mgr-reorder Moritz, Hao Could these 3 patches go into fpga-next now ? Tom > fpga: m10bmc-sec: add max10 secure update functions