On 23/11/18 11:56, BALATON Zoltan wrote: > On Fri, 23 Nov 2018, Philippe Mathieu-Daudé wrote: >> On 22/11/18 22:56, BALATON Zoltan wrote: >>> While we're there, should I also add pc-bios/canyonlands.dts which is >>> the device tree for sam460ex? >> >> Yes, I suggest this set: >> >> pc-bios/canyonlands.dt? >> pc-bios/u-boot-sam460* >> roms/u-boot-sam460ex > > Well, canyonlands.dtb and u-boot-sam460-*.bin are binaries built from > canyonlands.dts and roms/u-boot-sam460ex respectively and > roms/u-boot-sam460ex is mirrored from my git repo. So should these be > added despite of this or is it enough to add canyonlands.dts? I thought > only sources are listed in MAINTAINERS not binaries or external sources.
Hmm I see various binaries, i.e.: $ file pc-bios/s390-ccw.img pc-bios/s390-ccw.img: ELF 64-bit MSB shared object, IBM S/390, version 1 (SYSV), dynamically linked, interpreter /lib/ld64.so.1, BuildID[sha1]=5bf569bf2205ea94a015c1fe2702d7efb446a8c5, stripped $ ./scripts/get_maintainer.pl -f pc-bios/s390-ccw.img Christian Borntraeger <borntrae...@de.ibm.com> (supporter:S390-ccw boot) Thomas Huth <th...@redhat.com> (supporter:S390-ccw boot) Cornelia Huck <coh...@redhat.com> (supporter:S390) qemu-s3...@nongnu.org (open list:S390-ccw boot) $ file pc-bios/u-boot.e500 pc-bios/u-boot.e500: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), statically linked, stripped $ ./scripts/get_maintainer.pl -f pc-bios/u-boot.e500 David Gibson <da...@gibson.dropbear.id.au> (odd fixer:e500) qemu-...@nongnu.org (open list:e500) If I have issues with a binary like 'canyonlands.dtb' I'd like to be able to contact the maintainer. Maybe this is not the best example since the 'canyonlands.dts' is there too ;) Regards, Phil.
