linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: 楊宗翰 <ecs.taipeikernel@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Bob Moragues" <moragues@chromium.org>, Harvey <hunge@google.com>,
	"Stephen Boyd" <swboyd@chromium.org>,
	"Andy Gross" <agross@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	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
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Adding DT binding for zombie
Date: Mon, 28 Nov 2022 08:20:36 -0800	[thread overview]
Message-ID: <CAD=FV=X4GzCnmgnAQMzCNpCxzxkZXWONt4gNVCHniRYE_uFVyg@mail.gmail.com> (raw)
In-Reply-To: <Y343IWgkli+y8HMn@google.com>

Hi,

On Wed, Nov 23, 2022 at 7:07 AM Matthias Kaehlcke <mka@chromium.org> wrote:
>
> > My checkout steps as below:
> > $ git remote add linux_qcom git://git.kernel.org/pub/scm/linux/kernel/git/
> > qcom/linux.git
> > $ git fetch --no-tags linux_qcom
> > $ git checkout -b <MyLocalBranchName> linux_qcom/for-next
> >
> > Is my code base branch still worng?  Am I missing something?Â
>
> 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-${version}'
> 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

  reply	other threads:[~2022-11-28 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 12:37 [PATCH v2 1/2] dt-bindings: arm: qcom: Adding DT binding for zombie Owen Yang
2022-11-22 12:37 ` [PATCH v2 2/2] arm64: dts: qcom: sc7280: Add DT for sc7280-herobrine-zombie Owen Yang
2022-11-22 13:30   ` Matthias Kaehlcke
2022-11-22 14:14 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Adding DT binding for zombie Matthias Kaehlcke
2022-11-22 14:28 ` Matthias Kaehlcke
     [not found]   ` <CAPao8GKpXcRm3PmWnv+rsr2z53r6J-ScXAq+fOi4ydQg_Gy31A@mail.gmail.com>
2022-11-23 15:07     ` Matthias Kaehlcke
2022-11-28 16:20       ` Doug Anderson [this message]
2022-11-28 17:07         ` Matthias Kaehlcke
2022-11-28 18:51           ` Doug Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD=FV=X4GzCnmgnAQMzCNpCxzxkZXWONt4gNVCHniRYE_uFVyg@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=Abner.Yen@ecs.com.tw \
    --cc=Darren.Chen@ecs.com.tw \
    --cc=Gavin.Lee@ecs.com.tw \
    --cc=Jason.Huang@ecs.com.tw \
    --cc=Vicy.Lee@ecs.com.tw \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ecs.taipeikernel@gmail.com \
    --cc=hunge@google.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=moragues@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=swboyd@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).