public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivian Wang <wangruikang@iscas.ac.cn>
To: Mark Brown <broonie@kernel.org>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Networking <netdev@vger.kernel.org>, Yixun Lan <dlan@gentoo.org>
Cc: Guodong Xu <guodong@riscstar.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the net-next tree with the spacemit tree
Date: Wed, 17 Sep 2025 19:48:34 +0800	[thread overview]
Message-ID: <597466da-643d-4a75-b2e8-00cf7cf3fcd0@iscas.ac.cn> (raw)
In-Reply-To: <aMqby4Cz8hn6lZgv@sirena.org.uk>

Hi all,

On 9/17/25 19:30, Mark Brown wrote:
> [...]
>
>   3c247a6366d58 ("riscv: dts: spacemit: Add Ethernet support for BPI-F3")
>   e32dc7a936b11 ("riscv: dts: spacemit: Add Ethernet support for Jupiter")
>
> from the net-next tree.

I originally submitted these net-next patches [1]. AFAICT, this is the
correct conflict resolution. Thank you.

Just FYI, Yixun has proposed for net-next to back out of the DTS changes
and taking them up through the spacemit tree instead [1], resolving the
conflicts in the spacemit tree. This would certainly mean less headaches
while managing pull requests, as well as allowing Yixun to take care of
code style concerns like node order. However, I do not know what the
norms here are.

Vivian "dramforever" Wang

[1]: https://lore.kernel.org/spacemit/20250914-net-k1-emac-v12-0-65b31b398f44@iscas.ac.cn/
[2]: https://lore.kernel.org/spacemit/20250916122026-GYB1255161@gentoo.org/


  reply	other threads:[~2025-09-17 11:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 11:30 linux-next: manual merge of the net-next tree with the spacemit tree Mark Brown
2025-09-17 11:48 ` Vivian Wang [this message]
2025-09-17 12:03   ` Mark Brown
2025-09-17 12:30     ` Yixun Lan
2025-09-17 12:59       ` Yixun Lan
2025-09-19  9:25         ` Yixun Lan

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=597466da-643d-4a75-b2e8-00cf7cf3fcd0@iscas.ac.cn \
    --to=wangruikang@iscas.ac.cn \
    --cc=broonie@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dlan@gentoo.org \
    --cc=guodong@riscstar.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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