This website works better with JavaScript.
Explore
Register
Sign In
kernel
/
dtc
mirror of
https://git.kernel.org/pub/scm/utils/dtc/dtc.git
Watch
1
Star
0
Fork
You've already forked dtc
0
Code
Issues
Projects
Releases
Wiki
Activity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
914
Commits
2
Branches
23
Tags
1.7 MiB
Tree:
c18bae9a4c
main
master
RHEL-7.4
dwg-last
v1.0.0
v1.0.0-rc1
v1.1.0
v1.1.0-rc1
v1.2.0
v1.2.0-rc1
v1.2.0-rc2
v1.3.0
v1.4.0
v1.4.1
v1.4.2
v1.4.3
v1.4.4
v1.4.5
v1.4.6
v1.4.7
v1.5.0
v1.5.1
v1.6.0
v1.6.1
v1.7.0
Branches
Tags
${ item.name }
Create tag
${ searchTerm }
Create branch
${ searchTerm }
from 'c18bae9a4c'
${ noResults }
dtc
/
tests
/
stacked_overlay_base_nolabe...
7 lines
56 B
Raw
Normal View
History
Unescape
Escape
fdtoverlay: Allow adding labels to __overlay__ nodes in overlays When applying overlays, we merge symbols from the overlay into the target tree. At the moment the logic for this assumes all symbols in the overlay are attached to a node of the form: /fragment@XXX/__overlay__/relative/path And will end up applied to the relative/path node under the fragment's target. However, this disallows the case of a symbol in the form just: /fragment@XXX/__overlay__ This does have a pretty obvious sensible meaning: attach the new symbol directly to the fragment's target, but we don't currently do that. It's pretty easy to workaround this limitation in one's overlays, but it's also easy to handle in the overlay applying code, so we might as well extend it to cover this case. Reported-by: Christophe Braillon Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
6 years ago
/dts-v1/;
/ {
foonode {
foo-property = "foo";
};
};