From: Igor Opaniuk
Allow the '+' symbol as a valid character in filenames listed in the
IMAGE_EFI_BOOT_FILES variable.
The '+' symbol might be used to support boot counting for boot entries,
as described in the UAPI Boot Loader Specification [1]:
The boot counting data is stored in the name of
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1].
The list of files:
$ find . -type f -name "*.md"
./README.qemu.md
./MAINTAINERS.md
./README.OE-Core.md
./meta/lib/patchtest/README.md
./meta/recipes-devtools/rust/README-rust.md
./meta/recipes-devtools/perl-cross/files/REA
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1]:
$ cat ./meta/recipes-devtools/rust/README-rust.md | mdl
(stdin):1: MD002 First header should be a top level header
(stdin):25: MD006 Consider starting bulleted lists at the beginning of the line
(stdin):3: MD009 Trailing s
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1]:
$ cat ./meta/lib/patchtest/README.md | mdl
(stdin):4: MD034 Bare URL used
(stdin):8: MD034 Bare URL used
(stdin):9: MD034 Bare URL used
(stdin):20: MD034 Bare URL used
[1] https://github.com/markdownlint/markdownlint
Sign
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1]:
$ cat README.qemu.md | mdl
(stdin):8: MD006 Consider starting bulleted lists at the beginning of the line
[1] https://github.com/markdownlint/markdownlint
Signed-off-by: Igor Opaniuk
---
README.qemu.md | 8
1 f
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1]:
$ cat SECURITY.md | mdl
(stdin):16: MD013 Line length
(stdin):19: MD013 Line length
(stdin):20: MD013 Line length
(stdin):1: MD026 Trailing punctuation in header
(stdin):6: MD034 Bare URL used
(stdin):16: MD034 Bare URL us
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1]:
$ cat MAINTAINERS.md | mdl
(stdin):71: MD012 Multiple consecutive blank lines
(stdin):72: MD012 Multiple consecutive blank lines
[1] https://github.com/markdownlint/markdownlint
Signed-off-by: Igor Opaniuk
---
MAINTAINER
From: Igor Opaniuk
Fix markdown style issues using markdownlint tool [1]:
$ cat README.OE-Core.md | mdl
(stdin):15: MD012 Multiple consecutive blank lines
(stdin):9: MD034 Bare URL used
(stdin):13: MD034 Bare URL used
(stdin):19: MD034 Bare URL used
(stdin):25: MD046 Code block style
(stdin):29:
On Thu, Jan 30, 2025 at 1:48 PM Igor Opaniuk via
lists.openembedded.org
wrote:
>
> From: Igor Opaniuk
>
> Allow the '+' symbol as a valid character in filenames listed in the
> IMAGE_EFI_BOOT_FILES variable.
>
> The '+' symbol might be used to sup
From: Igor Opaniuk
Allow the '+' symbol as a valid character in filenames listed in the
IMAGE_EFI_BOOT_FILES variable.
The '+' symbol might be used to support boot counting for boot entries,
as described in the UAPI Boot Loader Specification [1]:
The boot counting data is stored in the name of
From: Igor Opaniuk
create_image_spdx() implementation assumes that image is indeed a file.
If image recipe deploys a directory (for example, which contains an
hierarchy of flash artifacts, that is used by SoC vendor-specific
flashing tool) which follows ${IMAGE_NAME}.${IMAGE_TYPE} naming scheme,
On Mon, Jan 13, 2025 at 8:30 PM Joshua Watt wrote:
>
> On Mon, Jan 13, 2025 at 10:51 AM wrote:
> >
> > From: Igor Opaniuk
> >
> > create_image_spdx() implementation assumes that image is indeed a file.
> > If image recipe deploys a directory (for example, which contains an
> > hierarchy of flash
From: Igor Opaniuk
create_image_spdx() implementation assumes that image is indeed a file.
If image recipe deploys a directory (for example, which contains an
hierarchy of flash artifacts, that is used by SoC vendor-specific
flashing tool) which follows ${IMAGE_NAME}.${IMAGE_TYPE} naming scheme,
Hello Joshua,
On Mon, Jan 13, 2025 at 3:58 PM Joshua Watt wrote:
>
> On Mon, Jan 13, 2025 at 5:34 AM Igor Opaniuk via
> lists.openembedded.org
> wrote:
> >
> > From: Igor Opaniuk
> >
> > create_image_spdx() implementation assumes that image is indeed a
From: Igor Opaniuk
create_image_spdx() implementation assumes that image is indeed a file.
If image recipe deploys a directory (for example, which contains an
hierarchy of flash artifacts, that is used by SoC vendor-specific
flashing tool) which follows ${IMAGE_NAME}.${IMAGE_TYPE} naming scheme,
On Tue, May 21, 2024 at 4:28 PM Igor Opaniuk via
lists.openembedded.org
wrote:
>
> Add support for force reboot in the case of fatal error. In some cases
> it's better to force reboot (especially when hw watchdog is not
> engaged) instead of waiting for 3600 seconds, for ex
Add support for force reboot in the case of fatal error. In some cases
it's better to force reboot (especially when hw watchdog is not
engaged) instead of waiting for 3600 seconds, for example in order to
trigger some recovery procedure during next boot procedure
(after unsuccessful OTA update etc)
Add support for force reboot in the case of fatal error. In some cases
it's better to force reboot (especially when hw watchdog is not
engaged) instead of waiting for 3600 seconds, for example in order to
trigger some recovery procedure during next boot procedure
(after unsuccessful OTA update etc)
Hello Alex,
On Tue, May 21, 2024 at 1:17 PM Alexander Kanavin
wrote:
>
> Seems ok to me, you can resend without the RFC.
I'll just send v2 without the RFC tag, thanks!
>
> Alex
>
> On Mon, 20 May 2024 at 17:31, Igor Opaniuk via lists.openembedded.org
> wrote:
>
Add support for force reboot in the case of fatal error. In some cases
it's better to force reboot (especially when hw watchdog is not
engaged) instead of waiting for 3600 seconds, for example in order to
trigger some recovery procedure during next boot procedure
(after unsuccessful OTA update etc)
20 matches
Mail list logo