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=-3.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS 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 2B20CC43603 for ; Tue, 10 Dec 2019 10:20:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F22B12053B for ; Tue, 10 Dec 2019 10:20:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="NeYakiUC"; dkim=pass (1024-bit key) header.d=amazonses.com header.i=@amazonses.com header.b="VuITrJj+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727296AbfLJKUH (ORCPT ); Tue, 10 Dec 2019 05:20:07 -0500 Received: from a27-18.smtp-out.us-west-2.amazonses.com ([54.240.27.18]:50886 "EHLO a27-18.smtp-out.us-west-2.amazonses.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727032AbfLJKUH (ORCPT ); Tue, 10 Dec 2019 05:20:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=zsmsymrwgfyinv5wlfyidntwsjeeldzt; d=codeaurora.org; t=1575973206; h=From:To:Cc:Subject:References:Date:In-Reply-To:Message-ID:MIME-Version:Content-Type; bh=0Kb+E+8ZdD4D68+aCTRlNTqRFi3yA4uuBGG8Rr2pQgY=; b=NeYakiUCjcRoxcFOZnt6eDM0Jw6DgF/tnZftTAXzQSXZCBTLtVUHjodLxZvTXBDH Hq9okvn8vJADB+4lLhu1iExlQjDCa2avyXGPQiQ2N28sL2jhNW2J3eUnPftbCBE0sjS 8zvVlxy4TRDsGNGGSfBhTwmNwz1AXdSkjIZLROms= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=gdwg2y3kokkkj5a55z2ilkup5wp5hhxx; d=amazonses.com; t=1575973206; h=From:To:Cc:Subject:References:Date:In-Reply-To:Message-ID:MIME-Version:Content-Type:Feedback-ID; bh=0Kb+E+8ZdD4D68+aCTRlNTqRFi3yA4uuBGG8Rr2pQgY=; b=VuITrJj+QGHSbjoRYgHcNgD5stmzkqoubp1qS/rPYXMmGRDKHEZ+1XFtF503+RoY vZEjZl3cu1aydYOch0/P/dlSIWprQbnvW3xoRg52LTx6/OAKq52uqvIJOIT+pqxMXjJ +VfRIbeZnjfCG+yBJSf+s9Lz9Vf5FAcJAaECBda8= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org B3419C447AA Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; spf=none smtp.mailfrom=kvalo@codeaurora.org From: Kalle Valo To: Soeren Moch Cc: Wright Feng , Arend van Spriel , Franky Lin , Hante Meuleman , Chi-Hsien Lin , linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com, brcm80211-dev-list@cypress.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/8] brcmfmac: reset two D11 cores if chip has two D11 cores References: <20191209223822.27236-1-smoch@web.de> <0101016eef117d24-d6de85e6-6356-4c73-bff4-f787e8c982bc-000000@us-west-2.amazonses.com> Date: Tue, 10 Dec 2019 10:20:06 +0000 In-Reply-To: (Soeren Moch's message of "Tue, 10 Dec 2019 11:14:22 +0100") Message-ID: <0101016eef52b82d-f791d0d8-d317-4050-9e8a-07a3fa7dafd8-000000@us-west-2.amazonses.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SES-Outgoing: 2019.12.10-54.240.27.18 Feedback-ID: 1.us-west-2.CZuq2qbDmUIuT3qdvXlRHZZCpfZqZ4GtG9v3VKgRyF0=:AmazonSES Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Soeren Moch writes: > On 10.12.19 10:08, Kalle Valo wrote: >> Soeren Moch writes: >> >>> From: Wright Feng >>> >>> There are two D11 cores in RSDB chips like 4359. We have to reset two >>> D11 cores simutaneously before firmware download, or the firmware may >>> not be initialized correctly and cause "fw initialized failed" error. >>> >>> Signed-off-by: Wright Feng >> Soeren's s-o-b missing at least in patches 1, 6 and 7. Please read: >> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#signed-off-by_missing >> > > OK, also for unmodified patches another s-o-b is required. Yes, every patch you submit needs to have your s-o-b to mark that you agree with Developer's Certificate of Origin. https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches