From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robherring2@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Pingfan Liu <kernelfans@gmail.com>, Rob Herring <robh@kernel.org>
Subject: linux-next: manual merge of the devicetree tree with the devicetree-fixes tree
Date: Wed, 22 Dec 2021 15:51:56 +1100 [thread overview]
Message-ID: <20211222155156.22a172c7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Hi all,
Today's linux-next merge of the devicetree tree got a conflict in:
include/linux/of_fdt.h
between commit:
7ca964c3978d ("efi: apply memblock cap after memblock_add()")
from the devicetree-fixes tree and commits:
60f20d84dc81 ("of/fdt: Rework early_init_dt_scan_chosen() to call directly")
1f012283e936 ("of/fdt: Rework early_init_dt_scan_memory() to call directly")
from the devicetree 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.
--
Cheers,
Stephen Rothwell
diff --cc include/linux/of_fdt.h
index ad09beb6d13c,914739f3c192..000000000000
--- a/include/linux/of_fdt.h
+++ b/include/linux/of_fdt.h
@@@ -58,11 -58,8 +58,9 @@@ extern int of_flat_dt_is_compatible(uns
extern unsigned long of_get_flat_dt_root(void);
extern uint32_t of_get_flat_dt_phandle(unsigned long node);
- extern int early_init_dt_scan_chosen(unsigned long node, const char *uname,
- int depth, void *data);
- extern int early_init_dt_scan_memory(unsigned long node, const char *uname,
- int depth, void *data);
+ extern int early_init_dt_scan_chosen(char *cmdline);
+ extern int early_init_dt_scan_memory(void);
+extern void early_init_dt_check_for_usable_mem_range(void);
extern int early_init_dt_scan_chosen_stdout(void);
extern void early_init_fdt_scan_reserved_mem(void);
extern void early_init_fdt_reserve_self(void);
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-12-22 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 4:51 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-01 4:46 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=20211222155156.22a172c7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robherring2@gmail.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
all inboxes | Powered by JetHome®