Lines Matching refs:will
77 letters and dashes instead of underscores. This rule will apply to all
193 owners will have the overall responsibility of the contents of a
194 Zephyr module repository. In particular, a module owner will:
313 Any new content to be added in a module repository will require to have
434 line variable :makevar:`EXTRA_ZEPHYR_MODULES` will take precedence.
463 The name should be specified in the :file:`zephyr/module.yml` file. This will
490 If the ``name`` field is not specified then the Zephyr module name will be
492 As example, the Zephyr module located in :file:`<workspace>/modules/bar` will
614 When a module has a :file:`module.yml` file, it will automatically be included into
737 a function which will be invoked by sysbuild at a pre-defined point in the
753 - ``<images>`` is the list of Zephyr images that will be created by the build system.
798 This example will ensure that ``bar`` is present when ``foo`` is included into
799 the build system, and it will also ensure that ``bar`` is processed before
1018 - ``url``: URL that identifies the location the blob will be fetched from, as
1070 content of that file will be used to determine which files should be added
1076 is considered a module, and those files will be added to the build.
1125 yourself, then no additional modules are added to the build. You will still be
1146 merged, the revision will need to be changed either by the submitter or by the
1150 using exactly the same process. In this case you will change multiple entries of
1161 If the request is approved, a new repository will
1170 Maintainers from the Zephyr project will create the repository and initialize
1171 it. You will be added as a collaborator in the new repository. Submit the