From: Max Krummenacher <max.oss.09@gmail.com>
To: Ryan Eatmon <reatmon@ti.com>
Cc: Neha Malcom Francis <n-francis@ti.com>,
sjg@chromium.org, vigneshr@ti.com, bb@ti.com, m-chawdhry@ti.com,
alpernebiyasak@gmail.com, nm@ti.com, u-boot@lists.denx.de,
vishalm@ti.com, jonas@kwiboo.se, sughosh.ganu@linaro.org
Subject: Re: [PATCH v2 2/2] tools: binman: ti_board_cfg: Check for linting problems
Date: Tue, 23 Jan 2024 11:06:32 +0100 [thread overview]
Message-ID: <Za-PqGxk6is1ToLc@toolbox> (raw)
In-Reply-To: <419c31bd-7cd8-4439-b001-adad75184cf9@ti.com>
On Mon, Jan 22, 2024 at 03:11:35PM -0600, Ryan Eatmon wrote:
>
>
> On 1/22/2024 6:59 AM, Max Krummenacher wrote:
> > Hi
> >
> > On Fri, Jan 05, 2024 at 05:09:17PM +0530, Neha Malcom Francis wrote:
> > > Use yamllint for checking whether YAML configuration files are adhering
> > > to default yamllint rules.
> >
> > If I understand this correctly this patch now runs checks to verify
> > that yaml files which are part of the U-Boot source tree are correct.
> >
> > Shouldn't this be done when one commits a yaml file, i.e. in U-Boot CI
> > rather than repeating the process on every build and thus having an
> > additional dependency to build U-Boot and additional build time?
> >
> > Note that in openembedded there is currently no python yamllint
> > recipe providing the used python module in the regularly used layers.
> > How do you plan to integrate the change in the OE U-Boot recipe?
> > At least our OE CI of latest master now fails (for a TI AM62 based SoM)
> > as the python module is missing.
>
> I have submitted a patch to oe-core for this missing recipe.
>
> https://lists.openembedded.org/g/openembedded-core/message/194192
>
> Hopefully they accept it. Otherwise, we are going to "temporarily" carrying
> the same recipe in meta-ti-extras until they accept it in oe-core.
Hi Ryan
Thanks for looking into it.
Max
>
>
> > Regards
> > Max
> >
>
> --
> Ryan Eatmon reatmon@ti.com
> -----------------------------------------
> Texas Instruments, Inc. - LCPD - MGTS
prev parent reply other threads:[~2024-01-23 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 11:39 [PATCH v2 0/2] binman: ti_board_cfg: Add yamllint support Neha Malcom Francis
2024-01-05 11:39 ` [PATCH v2 1/2] board: ti: *-cfg.yaml: Adhere to yamllint rules Neha Malcom Francis
2024-01-19 16:08 ` Tom Rini
2024-01-05 11:39 ` [PATCH v2 2/2] tools: binman: ti_board_cfg: Check for linting problems Neha Malcom Francis
2024-01-19 16:08 ` Tom Rini
2024-01-22 12:59 ` Max Krummenacher
2024-01-22 21:11 ` Ryan Eatmon
2024-01-23 10:06 ` Max Krummenacher [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Za-PqGxk6is1ToLc@toolbox \
--to=max.oss.09@gmail.com \
--cc=alpernebiyasak@gmail.com \
--cc=bb@ti.com \
--cc=jonas@kwiboo.se \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=reatmon@ti.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox