Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp3739385pxv; Tue, 13 Jul 2021 02:35:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwvbkmQLFgBIXcjY8VBRJKeEtrqqLgZmqa7dAQ4IQBm0KLowueQNBnjANn47DqGp0DVSJrA X-Received: by 2002:a17:907:9495:: with SMTP id dm21mr4465637ejc.526.1626168944499; Tue, 13 Jul 2021 02:35:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626168944; cv=none; d=google.com; s=arc-20160816; b=nP/yY6enQ7n4on3RXqIALjekVmJqNEJ9VCiRV6cXsE9CItpjRgHQASyAr0QKkuxl4g J1XrjIAgwjY8nTF/k8sWRmc/ih53irkHloPe77XCeBYMvX+1mk1IAR9kAEeN2eFdvwPE +1ndS4nFCGNR1UqhIQohJ0KfMWJ1+bFYJw0Z0Za20nZzt3GFk9tZh/5S29EwbVr3jxu3 SW7ugzx0PHqQ3qKfVVPRT+qQ0JYqpHLyikS3dER4Q5g6Rm6DkErfSQ6uxYZ89ngL5t94 7oDd1A37zyWnmbGsDeQs2YC11Pp+DHHgXULGQlqxYhMiP3mfyBMAKF+th8oDvp7e7YRi dWTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=b7r3T3pS6asyUzdwl7dEf1TRPhZJJQjxXPBMr+MPlxE=; b=evKLtpZKXc9OynwSuXF2GkavbMiKhocdvg3s2ePUM0uhxbuolfBYaVu2yJRfNBLVN+ 8mjTy4cafRsfJD1PzYvtjMqob2zHGWHMFhrHBtNXYFiPhlxrmIcbKjA0m1JgqE2qayht VXH7exKrPs2t+Q5lGFtMdPsZ87GNehzhG9s7CMRhkGexh8QP155Xj00Wo9hPtiIIpLnH 3mVkmp4MHjpcdY3EDHGCDJ5E0AUw7SgBchpXIy7Ii38XRbex8p0lvJYmRx02kpVdBFnS rzJ6wO0OIIrWqnvf60DRvIpJ4cBXuGSiWQrHXH2wGmXyl7LzZFxJIB3hBGsEZZg2kIUh 5wYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@yadro.com header.s=mta-01 header.b=Ur2vjL8X; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=yadro.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s11si21631838edh.483.2021.07.13.02.35.21; Tue, 13 Jul 2021 02:35:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@yadro.com header.s=mta-01 header.b=Ur2vjL8X; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=yadro.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235222AbhGMJfM (ORCPT + 99 others); Tue, 13 Jul 2021 05:35:12 -0400 Received: from mta-02.yadro.com ([89.207.88.252]:41098 "EHLO mta-01.yadro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S234997AbhGMJfL (ORCPT ); Tue, 13 Jul 2021 05:35:11 -0400 Received: from localhost (unknown [127.0.0.1]) by mta-01.yadro.com (Postfix) with ESMTP id DBC8A45C91; Tue, 13 Jul 2021 09:32:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h= content-transfer-encoding:mime-version:user-agent:content-type :content-type:organization:references:in-reply-to:date:date:from :from:subject:subject:message-id:received:received:received; s= mta-01; t=1626168738; x=1627983139; bh=gD0UuHaFhtXE1CjYlSQQdnWtb kTcj4oOtAaKhS8m6Bo=; b=Ur2vjL8XI1D1BEPiiveK3sXgIHaUN24tyldZ6QS+v sPh3LOD4JsHronEa+gn29eap4R+jG+ST2TLf8zNiNpwhbBg5TCRYukspNCLAKjO1 hTQMmNN3TDsyOCWIGVi8V3aaWf6LeqHF2lWVUykRn7Yitl7w3uFbcFQ/CQOm/P6T gI= X-Virus-Scanned: amavisd-new at yadro.com Received: from mta-01.yadro.com ([127.0.0.1]) by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DlROguvzsDIE; Tue, 13 Jul 2021 12:32:18 +0300 (MSK) Received: from T-EXCH-03.corp.yadro.com (t-exch-03.corp.yadro.com [172.17.100.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mta-01.yadro.com (Postfix) with ESMTPS id 8D66149E06; Tue, 13 Jul 2021 12:32:18 +0300 (MSK) Received: from [10.199.0.247] (10.199.0.247) by T-EXCH-03.corp.yadro.com (172.17.100.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Tue, 13 Jul 2021 12:32:18 +0300 Message-ID: Subject: Re: [PATCH v2 3/3] net/ncsi: add dummy response handler for Intel boards From: Ivan Mikhaylov To: Joel Stanley CC: "David S . Miller" , Jakub Kicinski , Samuel Mendoza-Jonas , "Benjamin Herrenschmidt" , Networking , Linux Kernel Mailing List , OpenBMC Maillist Date: Tue, 13 Jul 2021 12:42:05 +0300 In-Reply-To: References: <20210708122754.555846-1-i.mikhaylov@yadro.com> <20210708122754.555846-4-i.mikhaylov@yadro.com> Organization: YADRO Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.199.0.247] X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To T-EXCH-03.corp.yadro.com (172.17.100.103) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2021-07-12 at 10:03 +0000, Joel Stanley wrote: > On Thu, 8 Jul 2021 at 12:28, Ivan Mikhaylov wrote: > > > > Add the dummy response handler for Intel boards to prevent incorrect > > handling of OEM commands. > > What do you mean? When you don't have proper OEM handler for your MFR_ID, you'll get this as example: [ 39.073873] ftgmac100 1e660000.ethernet eth1: Received unrecognized OEM packet with MFR-ID (0x157) [ 39.082974] ftgmac100 1e660000.ethernet eth1: NCSI: Handler for packet type 0xd0 returned -2 > Is this to handle the response to the link up OEM command? If so, > include it in the same patch. It is not the response, it's provides same way of handling as for broadcom and mellanox manufacturers. > Can you check that the response is to the link up command and print a > warning if not? Yes, I can. As example, ncsi_oem_smaf_mlx doesn't check the response, for me it's like unidirectional commands, same for this one. Thanks.