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=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 56292C3A5A2 for ; Fri, 23 Aug 2019 09:02:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 11D0D22CE3 for ; Fri, 23 Aug 2019 09:02:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="N7h77oRW" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732043AbfHWJCJ (ORCPT ); Fri, 23 Aug 2019 05:02:09 -0400 Received: from mail-lf1-f68.google.com ([209.85.167.68]:38485 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725797AbfHWJCJ (ORCPT ); Fri, 23 Aug 2019 05:02:09 -0400 Received: by mail-lf1-f68.google.com with SMTP id f21so1634320lfc.5 for ; Fri, 23 Aug 2019 02:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0QyxxyRluECjdJkoLMYC9fmu4/5/v8zNJ/ufvcfQSPQ=; b=N7h77oRWy1NES6UfXGLBy3+XgXDQfO9qbseQVAx7sYunjgOJVDezGdzBbBEZPDYbWs zdzwI+m8PrJ6XBzhs+0Ekab55i30Pzo1aOIJXZIRFTGYEmFJn5DjocBNqR2yP+BI6zDr UAC+vml6qtduEWXpluIDMfVVJMa3k6qPdGZXAz+P6UiD0SRX0xyH59MhxrKAfsyAcS6L zsC0wrwY83haDmjM4/xlhvqSWSUgWW8cKIV/WSuE97PIaLNy4wSh+bUcCnSfQOLecmKM efVpPfVry4LguDt5SN1lChKwVrYRajjxqDWo4dHcEfHK+nmBqBHS095kqUs3iQTwlQrA A+dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0QyxxyRluECjdJkoLMYC9fmu4/5/v8zNJ/ufvcfQSPQ=; b=dsssG7W+oxknqCcCmaZvDn//KrgEhNqAcvpMJKpIvE7qKvOaxQVgWdY3xhXdzEkeu+ DEF05CGtCR8S+H7eTNltT7wEANZPWs+12ETQAG8sEpo9UsqQVUXATBoHtWOm3QM64bLn o4zgR96G1opeG9Nl7eleYi4U9lke+WjRCzyVdDegDRfsg/LS4UaE40UBniR4ms6WEftI 1Hqd7f3s82Z47CfDRoIUq1ltcD35BbEEvc66yTTT6uXvaPHeE9jlHaOS9H9quF79Fhn+ lkTIcV+Oe4wc/dlAhAraiaazgS+MOtfLNEHfVS2ehFAJPbLH4xfZHawEhHhy8Pp50DXv r2Gg== X-Gm-Message-State: APjAAAXOGII3Jqw/a4+2gMiuZ8+oShFYu23VZyByVBzhdfkXBN5qYc0S AvKPGTUr9PEj47ZlupjAKHxVUAWGjI5M7eGa0GVqFG018ss= X-Google-Smtp-Source: APXvYqyjQKopZCrPLomiHMDFj6TSJhVXJMVerAdTPrlxpQ37K5/d0izNNRhU1ncoS8elL1MPDL1F8PWM2sqeBfHF8YI= X-Received: by 2002:ac2:5c42:: with SMTP id s2mr2195029lfp.61.1566550927617; Fri, 23 Aug 2019 02:02:07 -0700 (PDT) MIME-Version: 1.0 References: <20190820080527.11796-1-linus.walleij@linaro.org> <5D5FA478.6090707@hisilicon.com> In-Reply-To: <5D5FA478.6090707@hisilicon.com> From: Linus Walleij Date: Fri, 23 Aug 2019 11:01:56 +0200 Message-ID: Subject: Re: [PATCH] gpio: Fix irqchip initialization order To: Wei Xu Cc: "open list:GPIO SUBSYSTEM" , Bartosz Golaszewski , Thierry Reding , Grygorii Strashko , Andy Shevchenko Content-Type: text/plain; charset="UTF-8" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Fri, Aug 23, 2019 at 10:31 AM Wei Xu wrote: > Yes, this fixes the problem and tested based on gpio/devel branch. > So, > > Tested-by: Wei Xu Awesome! Thanks a lot Wei! I'll get this to Torvalds tree ASAP. Yours, Linus Walleij