From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Takashi Iwai <tiwai@suse.de>, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Mark Brown" <broonie@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: linux-next: manual merge of the sound tree with the arm-soc tree
Date: Fri, 17 Feb 2023 11:23:27 +1100 [thread overview]
Message-ID: <20230217112327.5697baab@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
Hi all,
Today's linux-next merge of the sound tree got conflicts in:
sound/soc/cirrus/ep93xx-ac97.c
sound/soc/pxa/e740_wm9705.c
sound/soc/pxa/e750_wm9705.c
sound/soc/pxa/e800_wm9712.c
sound/soc/ti/davinci-vcif.c
between commits:
2b45e1fa9398 ("ASoC: remove unused ep93xx files")
efe81e9a9273 ("ASoC: remove unused davinci support")
b401d1fd8053 ("ASoC: pxa: remove unused board support")
from the arm-soc tree and commits:
f2211ac36ab0 ("ASoC: pxa: e740_wm9705: Drop empty platform remove function")
4ed923e8076b ("ASoC: pxa: e750_wm9705: Drop empty platform remove function")
394296eee2c2 ("ASoC: pxa: e800_wm9712: Drop empty platform remove function")
0e478b88b257 ("ASoC: cirrus: use helper function")
2abde57fb82b ("ASoC: ti: use helper function")
from the sound tree.
I fixed it up (I just removed the files) 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 --]
next reply other threads:[~2023-02-17 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 0:23 Stephen Rothwell [this message]
2023-02-20 22:27 ` linux-next: manual merge of the sound tree with the arm-soc tree Stephen Rothwell
2023-02-21 22:12 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-09-16 4:58 Stephen Rothwell
2024-09-16 8:42 ` Uwe Kleine-König
2024-09-17 23:57 ` Stephen Rothwell
2019-02-25 1:36 Stephen Rothwell
2019-02-25 9:19 ` Arnd Bergmann
2019-02-25 11:14 ` Takashi Iwai
2019-02-25 11:24 ` Sameer Pujar
2019-02-25 13:38 ` Arnd Bergmann
2019-02-25 16:43 ` Mark Brown
2011-10-11 4:43 Stephen Rothwell
2011-10-11 6:15 ` Ujfalusi, Peter
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=20230217112327.5697baab@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tiwai@suse.de \
--cc=u.kleine-koenig@pengutronix.de \
/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