Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CF08DC678D4 for ; Tue, 7 Mar 2023 12:49:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229684AbjCGMtR (ORCPT ); Tue, 7 Mar 2023 07:49:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43818 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229635AbjCGMtN (ORCPT ); Tue, 7 Mar 2023 07:49:13 -0500 Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 76E4B7B992 for ; Tue, 7 Mar 2023 04:49:12 -0800 (PST) Received: by mail-yb1-xb33.google.com with SMTP id e194so11258291ybf.1 for ; Tue, 07 Mar 2023 04:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678193351; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=7XIqvRUKvQi+9JwXJqk6zez0fEefEYHQDHJYoFfFR+A=; b=rLt1p1SNjdPluxKsu++nLxNZQwpVEkRtWzWUCcFxSG0c1fQFKSfOGx6QIpKAgezf2s 5Lv/iA4ARtZr61sN69lXr2Eu0S34rjvmJJiXA5/rv1vDZ7P2GPOovLB9/XDOJFxw9C3M oLKQ5mSRFQyfRDikwk8wdHorn+brKP95FY67X9DcHfR4FDmZlZJFM3ZgIbLYcQlkENnn bD6d9csZj2pWHorjM2kw/8/6vXWyrTBtwPEOI+JACS9ySb1TWK0F/ikoFUvEIG+dslbl j6Sput8UzaDGzRo2UCtGj0ce7yT3aBu8nzgIWZ6OROXseegOxGOfqbJwS4MhMunOo4GW g8Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678193351; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=7XIqvRUKvQi+9JwXJqk6zez0fEefEYHQDHJYoFfFR+A=; b=SyOrxCUssbzh+JiObz2949X1btpz4tKVtcdYcdQ+LaMWYLiu35xWcwg8B8CpPzf9yT E7YyTtCWN/cDnhYSYaC8rOWkrGinnKCfJmvSaC7NK33u+/OcZTA0woZKz8qeqIlMy59W Qpf3TkYwNqj1mKZVfIWzl6lnXLhc6Ity2oWQhotj8nOp5S7pryOlRYxAgRHlv0hwYei+ M2gsM7imkrZFz4XwEhyp8X3jPmm9PcC46Pv3UoCjtxEXAznij3N8M9Svn6TMxvyTZ2Et dmhS3fWqfXcXWLlWzOKeHEMi5HRoodfBvLwiirDr3myt7pROgpyG8ZzK3iLuikaS1Dbx oqFg== X-Gm-Message-State: AO0yUKXTQZsBHF+dYJMZWCc3wX7u6HdFxe84qw9qlyED5OdpbHKt3Wlp 4+SJpQpfx3diny/YaWlfhuMLHsSxDecUwRRblPdhSA== X-Google-Smtp-Source: AK7set91EayilxgeJgYG9wtl/O7pFWz++OFEQ6LsxD0etm1zImXNSTs+wbVLlvILysTuMohj7y6VGndYE/7U5GJKapA= X-Received: by 2002:a05:6902:4f4:b0:a06:5ef5:3a82 with SMTP id w20-20020a05690204f400b00a065ef53a82mr6731524ybs.5.1678193351638; Tue, 07 Mar 2023 04:49:11 -0800 (PST) MIME-Version: 1.0 References: <20230220023320.3499-1-clin@suse.com> In-Reply-To: From: Linus Walleij Date: Tue, 7 Mar 2023 13:49:00 +0100 Message-ID: Subject: Re: [PATCH v5 0/3] Add pinctrl support for S32 SoC family To: Andy Shevchenko Cc: Chester Lin , Rob Herring , Krzysztof Kozlowski , =?UTF-8?Q?Andreas_F=C3=A4rber?= , s32@nxp.com, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Larisa Grigore , Ghennadi Procopciuc , Andrei Stefanescu , Radu Pirea , Matthias Brugger Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 7, 2023 at 10:56 AM Andy Shevchenko wrote: > On Tue, Mar 7, 2023 at 11:22=E2=80=AFAM Linus Walleij wrote: > > On Tue, Mar 7, 2023 at 12:28 AM wrote: > > ... > > > > Can you unpull this? > > > If need be. > > > > Are there serious issues with the patch set such that they cannot be fi= xed > > by add-on patches? > > There are a few absent error checks, some error code shadowing, etc. > I can't tell if these all are serious, but the amount of them is like a d= ozen. > > I reviewed the patch, so you can look into that yourself and decide. I looked at it and some of the comments are pretty serious and need addressing ASAP. However it only affects this hardware so it's not like it's breaking the world. I generally prefer in-tree development over too many big patch iterations, it gets more focused. I think if Chester can follow up with a patch or several addressing the comments in the next week or two that's fine. However if we get closer to -rc6 and nothing has happened I would not be so happy and then I might just revert the driver patch. Yours, Linus Walleij