f5242d5ca1
Integrating the following commit(s) to linux-yocto/6.12:
1/4 [
Author: Bin Lan
Email: bin.lan.cn@windriver.com
Subject: fs/yaffs2: fix build warnings in yaffs_vfs.c when running make allyesconfig
Date: Mon, 9 Jun 2025 14:51:47 +0800
When building linux yocto with allyesconfig, some build warnings are found:
fs/yaffs2/yaffs_vfs.c:1292:15: error: no previous prototype for
‘yaffs_get_inode’ [-Werror=missing-prototypes]
1292 | struct inode *yaffs_get_inode(struct super_block *sb, int mode,
int dev,
| ^~~~~~~~~~~~~~~
fs/yaffs2/yaffs_vfs.c: In function ‘yaffs_iterate’:
fs/yaffs2/yaffs_vfs.c:1841:13: error: unused variable ‘i_version’
[-Werror=unused-variable]
1841 | u64 i_version;
| ^~~~~~~~~
fs/yaffs2/yaffs_vfs.c: At top level:
fs/yaffs2/yaffs_vfs.c:2441:16: error: no previous prototype for
‘yaffs2_get_parent’ [-Werror=missing-prototypes]
2441 | struct dentry *yaffs2_get_parent(struct dentry *dentry)
| ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Inspect the code that the two functions yaffs_get_inode() and
yaffs2_get_parent() are only used in the current file, i_version is not
used in the function yaffs_iterate(). So add the static modifier to the
two functions and remove the variable i_version.
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
2/4 [
Author: Bin Lan
Email: bin.lan.cn@windriver.com
Subject: fs/yaffs2: fix a build warning in yaffs_tagsmarshall.c when running make allyesconfig
Date: Mon, 9 Jun 2025 14:51:48 +0800
When building linux yocto with allyesconfig, a build warning is found:
fs/yaffs2/yaffs_tagsmarshall.c:188:6: error: no previous prototype for
‘yaffs_tags_marshall_install’ [-Werror=missing-prototypes]
188 | void yaffs_tags_marshall_install(struct yaffs_dev *dev)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Inspect the code that the function yaffs_tags_marshall_install() is
declared in this header file yaffs_tagsmarshall.h. So include the
header file in yaffs_tagsmarshall.c.
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
3/4 [
Author: Bin Lan
Email: bin.lan.cn@windriver.com
Subject: fs/yaffs2: fix a build warning in yaffs_yaffs2.c when running make allyesconfig
Date: Mon, 9 Jun 2025 14:51:49 +0800
When building linux yocto with allyesconfig, a build warning is
found:
fs/yaffs2/yaffs_yaffs2.c:557:21: error: no previous prototype for
‘yaffs2_do_endian_tnode_copy’ [-Werror=missing-prototypes]
557 | struct yaffs_tnode *yaffs2_do_endian_tnode_copy(struct yaffs_dev
*dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Inspect the code that the function yaffs2_do_endian_tnode_copy() is
only used in the current file. So add the static modifier to it.
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
4/4 [
Author: Bin Lan
Email: bin.lan.cn@windriver.com
Subject: fs/yaffs2: fix a build warning in yaffs_mtdif.c when running make allyesconfig
Date: Mon, 9 Jun 2025 14:51:50 +0800
When building linux yocto with allyesconfig, a build warning is
found:
fs/yaffs2/yaffs_mtdif.c:48:5: error: no previous prototype for
‘nandmtd_erase_block’ [-Werror=missing-prototypes]
48 | int nandmtd_erase_block(struct yaffs_dev *dev, int block_no)
| ^~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Inspect the code that the function nandmtd_erase_block() is
not used by yaffs2. So remove it.
Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
(From OE-Core rev: 8e139005a965425c5ca4e1d89b18666dfd26bbd1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 9b877748ef7a789fb75db525fec5568691745fef)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.