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 C94DDC433FE for ; Mon, 28 Nov 2022 16:20:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232397AbiK1QU5 (ORCPT ); Mon, 28 Nov 2022 11:20:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51336 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231135AbiK1QUx (ORCPT ); Mon, 28 Nov 2022 11:20:53 -0500 Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6B9D913E09 for ; Mon, 28 Nov 2022 08:20:52 -0800 (PST) Received: by mail-ej1-x62f.google.com with SMTP id gu23so8945087ejb.10 for ; Mon, 28 Nov 2022 08:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; 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=xB/MDsAyrTfDxbfwFpi7v9ob1ZeS88uoag9SCGEyi0g=; b=gap6/PEMlSFVcoD4M7/mMeS/+FbnSLroHAsUDRxbASrIxWgYTUKUihwqwoFmpHzXw+ 5GjFf7cOp03rcVcNkGNUZoIPqtNbHPx8hJX9bo5rxlYcSnVOgGrKltlfYrny0pFctp19 NSzPfKVoXE4Dh/eSjDPUFqii3IYwMoCQbjbnQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=xB/MDsAyrTfDxbfwFpi7v9ob1ZeS88uoag9SCGEyi0g=; b=dh/L0YvPa+EWfpsyoEbKn3cwLQ/kA3KcZdkn0+200iMa0zh5IT9Hv5KMoybJclXyMH XqAoaImISHAzuNUX3lSwSISXlMOWB1GJt9CpbYSsWHc7wUMkBdKj74j8PmyXClfD+nVx VPH1WFk6m/T0dTXtRWcFPelVKkEyg3PksrrpMPONb3xEJa6NMVSVPkpMInX2QVEsLCCv RYLwVXEUmGHnGG0/XLXb0+rPn+OVnp8yGN7nT1b/VUAmWqfnU0Njw9GI0eW+WY9ZyoPt qgFGkzCyup6PxXmlkQaQgm7OVktkExEZlyekeD7QhxreRJPhryC53KL3Zw9YnOcSLW9t TRYQ== X-Gm-Message-State: ANoB5pko8whPgXSgs1CVatWvibuHGKN6EA86DudvfJNF3EUPRyEtALdp IEqcYeeD/gFrfXiOTpZpyM4C74CaJNKlNe21 X-Google-Smtp-Source: AA0mqf5M0wL6ABew06PgmRyZbKo0nrTU2bZGkSailGjLbDORAvg8h9KIve0Kl5TIhArO5OFrerYlDg== X-Received: by 2002:a17:907:8a23:b0:7bd:2864:d33d with SMTP id sc35-20020a1709078a2300b007bd2864d33dmr13467160ejc.330.1669652450391; Mon, 28 Nov 2022 08:20:50 -0800 (PST) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com. [209.85.221.49]) by smtp.gmail.com with ESMTPSA id cz7-20020a0564021ca700b0046adde27bcasm3457468edb.38.2022.11.28.08.20.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Nov 2022 08:20:49 -0800 (PST) Received: by mail-wr1-f49.google.com with SMTP id w15so4494758wrl.9 for ; Mon, 28 Nov 2022 08:20:48 -0800 (PST) X-Received: by 2002:adf:fd89:0:b0:242:1f81:7034 with SMTP id d9-20020adffd89000000b002421f817034mr185921wrr.617.1669652448598; Mon, 28 Nov 2022 08:20:48 -0800 (PST) MIME-Version: 1.0 References: <20221122203635.v2.1.Ie05fd439d0b271b927acb25c2a6e41af7a927e90@changeid> In-Reply-To: From: Doug Anderson Date: Mon, 28 Nov 2022 08:20:36 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Adding DT binding for zombie To: Matthias Kaehlcke Cc: =?UTF-8?B?5qWK5a6X57+w?= , LKML , Bob Moragues , Harvey , Stephen Boyd , Andy Gross , Bjorn Andersson , Rob Herring , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, Abner.Yen@ecs.com.tw, Gavin.Lee@ecs.com.tw, Vicy.Lee@ecs.com.tw, Jason.Huang@ecs.com.tw, Darren.Chen@ecs.com.tw Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, Nov 23, 2022 at 7:07 AM Matthias Kaehlcke wrote: > > > My checkout steps as below: > > $ git remote add linux_qcom=C3=82 git://git.kernel.org/pub/scm/linux/ke= rnel/git/ > > qcom/linux.git > > $ git fetch --no-tags linux_qcom > > $ git checkout -b linux_qcom/for-next > > > > Is my=C3=82 code base branch still worng?=C3=82 Am I=C3=82 missing som= ething?=C3=82 > > My understanding is that it is best to base you changes on a branch like > 'arm64-for-6.2' as the 'for-next' branch is re-created every time changes > land in one of the '${area}-for-${version}' branches. > > No big issue in this case, just use the corresponding '${area}-for-${vers= ion}' > branch for future patches/versions :) FWIW, I usually just use Bjron's for-next branch for stuff like this. While the merge commits in the the Qualcomm "for-next" branch are re-created every time, because of the way "git" works the git hashes of the actual patches are the same as the git hashes of the patches in the separate branches. All the patches in "for-next" should be ones that are fine to base your patches on. -Doug