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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0A844C3A5A7 for ; Tue, 6 Dec 2022 08:43:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233724AbiLFInh (ORCPT ); Tue, 6 Dec 2022 03:43:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40900 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231771AbiLFIng (ORCPT ); Tue, 6 Dec 2022 03:43:36 -0500 Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DDC13DE8B for ; Tue, 6 Dec 2022 00:43:34 -0800 (PST) Received: by mail-lf1-x131.google.com with SMTP id b3so22556687lfv.2 for ; Tue, 06 Dec 2022 00:43:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=SaSD3geb2bQJh9N/RP9IsEjubJS5gEWgGuf2e7tOAdo=; b=sjhzeRgV7jr7bX4Q5DGBZ8RmwyS3taAXKME+uQhG21OQj57Z4Nh4Z9NQaLgXxXLF4Z gVyjJNPB7d5uNLBtHw48ksb231/XqWpbnBLZOcCQdtE7YGlQ+O+7Z8q8lGTi5jaZlT8v ti26RnFv91Y7u87la9aqRQR4+5kGkkahejIIFL0TUb9ozqRfI4CBNIBcTAKXoU4fTI74 KWRsYts15p4qHIxVASlI8lBYYNzKBvaUnatWmEKUrGADnsmwpjgDGxzx2g/Gn/DCoPat M2GUy3wkiYzmSDDUJRqA/aGvNlr4zl8uL6X5OF5+tbezwRRv0o2+biOu4NWlfvBgjg89 Z6Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=SaSD3geb2bQJh9N/RP9IsEjubJS5gEWgGuf2e7tOAdo=; b=Xn3QCI3CzYeK/4NI1y2ZSfBOUoq97Lbckr2RSdS9viNkuZfT97tV22ERI5Qx3WCno+ 1JM+FpCjd83Ir9DFBznYQLD6y3isLBSgBof+5fPdLEnlOGrh1SgHdulRWx3Xq4ROWZg0 phM/LgNTPIE1KHsQytXPGnZx5UIMMMsAHIw+B/f9tq8NDK+t2VsiZ9lQlNdaURtxhvLk PmQ2YzCYbPYVuc8KWfr881TubT9l+Au+0Y8sS2KkjO4Uv6691nm1b3cEBxCzTOe3sXqf 1EREgcDtjXDibFh1krusv/fKeVHhOaEUp9mMQ0lfHZIo16jCbbbrllHrDhe9hQzHd8I5 g6Gg== X-Gm-Message-State: ANoB5pnKrXeIC0/OyOvtHZxbSw4kuc2HKdc7OqLpw6Oz5AXyOYioHxGs oYlXthevr2y4Sh2EJSIhpIYZ9g== X-Google-Smtp-Source: AA0mqf7mR/e8/fiC7Foi5gFMjvFoZf6eTrsbwwZJo8KeirTkL3+gHpNzzBuTeDMmx8wswfW32qCzzQ== X-Received: by 2002:a05:6512:3189:b0:4b4:e3bd:6ca0 with SMTP id i9-20020a056512318900b004b4e3bd6ca0mr22528089lfe.278.1670316213184; Tue, 06 Dec 2022 00:43:33 -0800 (PST) Received: from [192.168.0.20] (088156142067.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.67]) by smtp.gmail.com with ESMTPSA id j6-20020a056512344600b004a27d2ea029sm2410648lfr.172.2022.12.06.00.43.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Dec 2022 00:43:32 -0800 (PST) Message-ID: Date: Tue, 6 Dec 2022 09:43:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: [PATCH] dt-bindings: soc: qcom: aoss: Add compatible for SM8550 Content-Language: en-US To: Bjorn Andersson Cc: Abel Vesa , Andy Gross , Konrad Dybcio , Rob Herring , Linux Kernel Mailing List , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org References: <20221116113128.2655441-1-abel.vesa@linaro.org> <20221205211623.extu4b22fsowilyd@builder.lan> From: Krzysztof Kozlowski In-Reply-To: <20221205211623.extu4b22fsowilyd@builder.lan> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 05/12/2022 22:16, Bjorn Andersson wrote: > On Wed, Nov 16, 2022 at 12:43:26PM +0100, Krzysztof Kozlowski wrote: >> On 16/11/2022 12:31, Abel Vesa wrote: >>> Document the compatible for SM8550. >>> >>> Signed-off-by: Abel Vesa >> >> Why this is not part of other SoC patches? I just received many single >> patches for this SM8550 topic. All these should be set of few series, >> not 10 or more... >> > > Because these patches are independent of each other and done in this way > means the maintainer can merge each piece on its own. I much prefer this > over having these series with 20+ patches being sent over and over > because one of the patches is getting feedback. But this one is patch for you, so should go with other patches targeting Qualcomm subarch. Before submission, we discussed extensively the proposed split per patches and it was agreed on. Yet this one here was a surprise. Best regards, Krzysztof