From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul@pwsan.com>
Cc: Jisheng Zhang <jszhang@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Vitaly Wool <vitaly.wool@konsulko.com>
Subject: linux-next: manual merge of the risc-v tree with the risc-v-fixes tree
Date: Wed, 9 Jun 2021 10:26:08 +1000 [thread overview]
Message-ID: <20210609102608.5582071b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Hi all,
Today's linux-next merge of the risc-v tree got a conflict in:
arch/riscv/mm/init.c
between commit:
8700a6b6fee2 ("riscv: fix typo in init.c")
from the risc-v-fixes tree and commit:
010623568222 ("riscv: mm: init: Consolidate vars, functions")
from the risc-v tree.
Note that 8700a6b6fee2 supposedly fixes 010623568222, but 010623568222
is not an ancestor of 8700a6b6fee2.
I fixed it up (I just used the version from 8700a6b6fee2) 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:[~2021-06-09 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 0:26 Stephen Rothwell [this message]
2021-06-09 0:37 ` linux-next: manual merge of the risc-v tree with the risc-v-fixes tree Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2024-06-28 13:48 Mark Brown
2023-04-20 12:40 broonie
2023-04-20 13:23 ` Alexandre Ghiti
2023-04-21 11:40 ` Mark Brown
2023-04-21 11:59 ` Mark Brown
2020-10-07 23:13 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=20210609102608.5582071b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul@pwsan.com \
--cc=vitaly.wool@konsulko.com \
/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