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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,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 81784C41604 for ; Tue, 6 Oct 2020 17:53:38 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BEA3B206CB for ; Tue, 6 Oct 2020 17:53:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BEA3B206CB Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4C5Q7M1zpxzDqDh for ; Wed, 7 Oct 2020 04:53:35 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=jae.hyun.yoo@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4C5Q5t1GpTzDqDb for ; Wed, 7 Oct 2020 04:52:17 +1100 (AEDT) IronPort-SDR: NQEQ0pAUsHKnCO0da5A77hP22yBINfMu//2xUh++GxjMlTDySAGJtRdxOC4rPSgNy2Dh0SXUix VUtNXTtGzMfw== X-IronPort-AV: E=McAfee;i="6000,8403,9765"; a="152371561" X-IronPort-AV: E=Sophos;i="5.77,343,1596524400"; d="scan'208";a="152371561" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2020 10:52:08 -0700 IronPort-SDR: XbwmFRn+9781+ya6Ph2r/jNrSusBX7YT1hK6MJlXQnbCgveNecAJIfTFcv4tLeAyzUGYFqUgzm iQzVzOUJMkXA== X-IronPort-AV: E=Sophos;i="5.77,343,1596524400"; d="scan'208";a="315763518" Received: from yoojae-mobl1.amr.corp.intel.com (HELO [10.255.228.213]) ([10.255.228.213]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2020 10:52:06 -0700 Subject: Re: PECI patchset status To: Joel Stanley , "Mihm, James" References: <20200903152753.GA57949@patrickw3-mbp.lan.stwcx.xyz> <20200903171556.GA32795@mauery.jf.intel.com> <20200904163430.GA3532@heinlein> From: Jae Hyun Yoo Message-ID: <251ba84a-a2ce-4000-e7bd-90685b9d3854@linux.intel.com> Date: Tue, 6 Oct 2020 10:51:54 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Vernon Mauery , OpenBMC Maillist Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" Hi Joel, On 9/28/2020 10:49 PM, Joel Stanley wrote: > On Fri, 11 Sep 2020 at 01:20, Mihm, James wrote: > >> Would it be acceptable for all of the 84+ Intel patches to reside in the openbmc repo while we work through the upstreaming process? >> Some of the patches require design changes and will take much longer to upstream. > > This is the intent of the openbmc tree. THe patches need to be posted, > in reviewable series, to be included. > > As discussed in this thread regarding the PECI patches, they have been > around for a long time without submission. They will need to be posted > upstream again before I put them in the OpenBMC tree. > > Early September, when this thread was started, was a great time to > make the PECI submission in terms of the upstream kernel development > cycle. The next best time is now. Thank you for carrying the out-of-tree PECI patch set so far. I really appreciate it. I agree with you that the PECI upstreaming should make a progress now but I'm still in unbalanced task priorities. I'll try to make it done as soon as possible but it's not available right now. As James already said, we'll use a forked tree if PECI patches are dropped off from OpenBMC linux tree v5.9, and it'll not be a permanent fork but just for a temporary and alternative way to minimize impact of dropping off the PECI patch set. Thanks for your understanding in advance. Best, Jae