[U-Boot] "best practice" for including common header file content?

more excruciatingly pedantic queries ... what is the best practice for header files under include/configs including common header files also in that same directory. i give you:
$ git grep zynq-common.h bitmain_antminer_s9.h:#include <configs/zynq-common.h> syzygy_hub.h: * See zynq-common.h for Zynq common configs syzygy_hub.h:#include <configs/zynq-common.h> topic_miami.h: * See zynq-common.h for Zynq common configs topic_miami.h:#include "zynq-common.h" zynq_cse.h: * See zynq-common.h for Zynq common configs zynq_cse.h:#include <configs/zynq-common.h> $
so some of them include "zynq-common.h", while others include <configs/zynq-common.h>. naturally, both work -- does u-boot have a stylistic preference?
rday

Hi,
On 09. 04. 19 13:18, Robert P. J. Day wrote:
more excruciatingly pedantic queries ... what is the best practice for header files under include/configs including common header files also in that same directory. i give you:
$ git grep zynq-common.h bitmain_antminer_s9.h:#include <configs/zynq-common.h> syzygy_hub.h: * See zynq-common.h for Zynq common configs syzygy_hub.h:#include <configs/zynq-common.h> topic_miami.h: * See zynq-common.h for Zynq common configs topic_miami.h:#include "zynq-common.h" zynq_cse.h: * See zynq-common.h for Zynq common configs zynq_cse.h:#include <configs/zynq-common.h> $
so some of them include "zynq-common.h", while others include <configs/zynq-common.h>. naturally, both work -- does u-boot have a stylistic preference?
I am not aware about any stylistic preference written anywhere.
Thanks, Michal
participants (2)
-
Michal Simek
-
Robert P. J. Day