All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 0/5] meta: fix trailing whitespace across classes, conf and recipes
Date: Sat, 15 Aug 2026 09:05:52 +0200	[thread overview]
Message-ID: <DKPBS41I2VXL.13RDKB81EOENQ@bootlin.com> (raw)
In-Reply-To: <20260813191615.34122-1-jaipaul.cheernam@est.tech>

On Thu Aug 13, 2026 at 9:16 PM CEST, Jaipaul Cheernam wrote:
> Fix all trailing whitespace warnings reported by bitbake during parsing.
> These were flagged on the Yocto autobuilder:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4405
>
> 53 files fixed across 5 patches, split by category:
> - classes-global (7 files)
> - classes-recipe (11 files)
> - classes (2 files)
> - conf (2 files)
> - recipes (31 files)
>

Hi Jaipaul,

Thanks for your patch.

It looks like you missed some of these:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4480/steps/22/logs/warnings
https://autobuilder.yoctoproject.org/valkyrie/#/builders/2/builds/4402/steps/14/logs/warnings

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-08-15  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 19:16 [PATCH 0/5] meta: fix trailing whitespace across classes, conf and recipes Jaipaul Cheernam
2026-08-13 19:16 ` [PATCH 1/5] classes-global: fix trailing whitespace Jaipaul Cheernam
2026-08-13 19:16 ` [PATCH 2/5] classes-recipe: " Jaipaul Cheernam
2026-08-13 19:16 ` [PATCH 3/5] classes: " Jaipaul Cheernam
2026-08-13 19:16 ` [PATCH 4/5] conf: " Jaipaul Cheernam
2026-08-13 19:16 ` [PATCH 5/5] recipes: " Jaipaul Cheernam
2026-08-15  7:05 ` Mathieu Dubois-Briand [this message]
2026-08-15  9:45   ` [OE-core] [PATCH 0/5] meta: fix trailing whitespace across classes, conf and recipes Richard Purdie

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=DKPBS41I2VXL.13RDKB81EOENQ@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=jaipaul.cheernam@est.tech \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.