From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Chanwoo Choi <cw00.choi@samsung•com>
Cc: "Linus Torvalds" <torvalds@linux-foundation•org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre•com>
Subject: linux-next: manual merge of the devfreq tree with the origin tree
Date: Mon, 9 Dec 2024 11:44:09 +1100 [thread overview]
Message-ID: <20241209114409.3cdd6fea@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi all,
Today's linux-next merge of the devfreq tree got conflicts in:
drivers/devfreq/event/exynos-nocp.c
drivers/devfreq/event/exynos-ppmu.c
drivers/devfreq/mtk-cci-devfreq.c
drivers/devfreq/rk3399_dmc.c
drivers/devfreq/sun8i-a33-mbus.c
between commit:
e70140ba0d2b ("Get rid of 'remove_new' relic from platform driver struct")
from the origin tree and commit:
1f8ac4b95fee ("PM / devfreq: Switch back to struct platform_driver::remove()")
from the devfreq tree.
I fixed it up (I just used the latter versions - only white space changes)
and can carry the fix as necessary. This is now fixed as far as linux-next
is concerned, but any non trivial conflicts should be mentioned to your
upstream maintainer when your tree is submitted for merging. You may
also want to consider cooperating with the maintainer of the conflicting
tree to minimise any particularly complex conflicts.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-12-09 0:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241209114409.3cdd6fea@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cw00.choi@samsung$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=u.kleine-koenig@baylibre$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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