From: Peter Chen <peter.chen@cixtech.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
soc@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: manual merge of the cix tree with the arm-soc tree
Date: Sat, 9 May 2026 09:16:11 +0800 [thread overview]
Message-ID: <af6K2w5uxcrbs3dR@nchen-desktop> (raw)
In-Reply-To: <a6925bf5-2ffe-45de-9ea8-90240a2abfa3@app.fastmail.com>
On 26-05-08 13:06:02, Arnd Bergmann wrote:
>
> Hi Peter,
>
> this is not a problem you caused, just something to be aware of
> when you send the pull request, and to check that Thierry made
> the right choice in resolving it.
>
> > Arnd, I deleted this patch at CIX next-tree. Would you please help queue it
> > in your soc/defconfig:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/cix.git/
> > branch: cix/defconfig
>
> Please send it as a normal pull request or patch to soc@lists.linux.dev
> so your change gets mered using the patchwork process.
>
> If you send it as a standalone patch, please make sure it applies
> on top of the soc/defconfig branch. A pull request is also fine,
> and that would normally be based on -rc1. Obviously this causes
> a merge conflict, which we will resolve during the merge.
>
Hi Arnd,
Thanks for explaining it. So, for linux-next merge confliction patch,
how to handle it better?
Option 1:
Send pull-request to SoC maintainer once linux-next merge conflict happens, and
depends on SoC maintainer's tree at linux-next for testing
Option 2:
Rebase on SoC maintainer's tree, and still keep patches on SoC submaintainer's tree
at linux-next for testing
Other options?
--
Best regards,
Peter
next prev parent reply other threads:[~2026-05-09 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 9:12 manual merge of the cix tree with the arm-soc tree Thierry Reding
2026-05-08 10:52 ` Peter Chen
2026-05-08 11:06 ` Arnd Bergmann
2026-05-09 1:16 ` Peter Chen [this message]
2026-05-09 8:02 ` Arnd Bergmann
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=af6K2w5uxcrbs3dR@nchen-desktop \
--to=peter.chen@cixtech.com \
--cc=arnd@arndb.de \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=soc@lists.linux.dev \
--cc=thierry.reding@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.