From: Takashi Iwai <tiwai@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>,
Baoquan He <hebaoquan@kylinos.cn>,
David Hildenbrand <david@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: linux-next: manual merge of the sound tree with the mm tree
Date: Mon, 05 Oct 2026 15:26:18 +0200 [thread overview]
Message-ID: <87bj98s2h1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261005061403.750dc014ce53e441a3ee6271@linux-foundation.org>
On Mon, 05 Oct 2026 15:14:03 +0200,
Andrew Morton wrote:
>
> On Mon, 5 Oct 2026 13:21:34 +0200 Mark Brown <broonie@kernel.org> wrote:
>
> > Hi all,
> >
> > Today's linux-next merge of the sound tree got a conflict in:
> >
> > sound/mips/snd-n64.c
> >
> > between commit:
> >
> > 0d62c52af5499 ("ALSA: n64: don't use GFP_DMA when calling dma_alloc_coherent()")
> >
> > from the mm tree and commit:
> >
> > e81f85fd3ca66 ("ALSA: mips: n64: Handle card removal properly")
> >
> > from the sound tree.
> >
> > I fixed it up (see below) 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.
>
> Thanks.
>
> Easy fix: move mm's little one-liner into the alsa tree.
>
> Takashi, please can you add this?
Sure, I applied now to sound.git tree for-next branch.
> I'll drop the mm.git copy now.
thanks,
Takashi
prev parent reply other threads:[~2026-10-05 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 11:21 Mark Brown
2026-10-05 13:14 ` Andrew Morton
2026-10-05 13:26 ` Takashi Iwai [this message]
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=87bj98s2h1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=hebaoquan@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®