From: Baoquan He <bhe@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ardb@kernel.org>,
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 asm-generic tree with the mm tree
Date: Mon, 18 Sep 2023 09:28:02 +0800 [thread overview]
Message-ID: <ZQenotf1QIHxovor@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230918101027.7506b71e@canb.auug.org.au>
On 09/18/23 at 10:10am, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the asm-generic tree got a conflict in:
>
> arch/ia64/kernel/setup.c
>
> between commit:
>
> 52f40d9a3c11 ("crash_core: change the prototype of function parse_crashkernel()")
Thanks a lot for fixing the conflict. I rebased the crash_core
refactoring code on linus's tree, so didn't notice ia64 arch has been
removed in next tree.
>
> from the mm tree and commit:
>
> cf8e8658100d ("arch: Remove Itanium (IA-64) architecture")
>
> from the asm-generic tree.
>
> I fixed it up (I removed the file) 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
next prev parent reply other threads:[~2023-09-18 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 0:10 linux-next: manual merge of the asm-generic tree with the mm tree Stephen Rothwell
2023-09-18 1:28 ` Baoquan He [this message]
2023-11-02 21:34 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 22:05 Stephen Rothwell
2024-01-10 22:22 ` Stephen Rothwell
2024-10-28 22:55 Stephen Rothwell
2024-11-21 23:56 ` Stephen Rothwell
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=ZQenotf1QIHxovor@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--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