From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Zhang Jiaming <jiaming@nfschina.com>
Subject: Re: linux-next: manual merge of the mm tree with the m68k tree
Date: Tue, 12 Jul 2022 10:47:24 +0200 [thread overview]
Message-ID: <CAMuHMdUdFwoHqwtH-eL3dc3s612fV4v7gYteuCZxZnPpHOFh-Q@mail.gmail.com> (raw)
In-Reply-To: <20220712184238.3670f277@canb.auug.org.au>
Hi Stephen,
On Tue, Jul 12, 2022 at 10:42 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Today's linux-next merge of the mm tree got a conflict in:
>
> arch/m68k/include/asm/sun3_pgtable.h
>
> between commit:
>
> c2a6236024b7 ("m68k: sun3: Fix spelling mistake")
>
> from the m68k tree and commit:
>
> e7911fea382d ("m68k/mm: enable ARCH_HAS_VM_GET_PAGE_PROT")
>
> from the mm tree.
>
> I fixed it up (the latter removed the comment that the former updated)
> 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.
Ah, right. The previous version of the m68k/mm patch didn't remove
the comment, so I thought the spelling fix was safe to apply.
I'll drop the spelling fix from the m68k for-v5.20 branch.
Thanks for reporting!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-07-12 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 8:42 Stephen Rothwell
2022-07-12 8:47 ` Geert Uytterhoeven [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=CAMuHMdUdFwoHqwtH-eL3dc3s612fV4v7gYteuCZxZnPpHOFh-Q@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=jiaming@nfschina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®