All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Cc: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
Subject: [PATCH 3/5] classes: fix trailing whitespace
Date: Thu, 13 Aug 2026 21:16:13 +0200	[thread overview]
Message-ID: <20260813191615.34122-4-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20260813191615.34122-1-jaipaul.cheernam@est.tech>

Fix trailing whitespace in classes bbclass files to resolve
bitbake parsing warnings.

Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
---
 meta/classes/image-buildinfo.bbclass | 2 +-
 meta/classes/useradd.bbclass         | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/classes/image-buildinfo.bbclass b/meta/classes/image-buildinfo.bbclass
index b83ce650ad..01636dac65 100644
--- a/meta/classes/image-buildinfo.bbclass
+++ b/meta/classes/image-buildinfo.bbclass
@@ -9,7 +9,7 @@
 # Usage: add INHERIT += "image-buildinfo" to your conf file
 #
 
-# Desired variables to display 
+# Desired variables to display
 IMAGE_BUILDINFO_VARS ?= "DISTRO DISTRO_VERSION"
 
 # Desired location of the output file in the image.
diff --git a/meta/classes/useradd.bbclass b/meta/classes/useradd.bbclass
index e9e835e1a2..aafd996fae 100644
--- a/meta/classes/useradd.bbclass
+++ b/meta/classes/useradd.bbclass
@@ -68,7 +68,7 @@ if test "x`echo $GROUPADD_PARAM | tr -d '[:space:]'`" != "x"; then
 		opts=`echo "$remaining" | cut -d ';' -f 1 | sed -e 's#[ \t]*$##'`
 		remaining=`echo "$remaining" | cut -d ';' -f 2- | sed -e 's#[ \t]*$##'`
 	done
-fi 
+fi
 
 if test "x`echo $USERADD_PARAM | tr -d '[:space:]'`" != "x"; then
 	echo "Running useradd commands..."
@@ -132,8 +132,8 @@ usermod_sysroot() {
 }
 
 common_useradd_sysroot() {
-	# Pseudo may (do_prepare_recipe_sysroot) or may not (do_populate_sysroot_setscene) be running 
-	# at this point so we're explicit about the environment so pseudo can load if 
+	# Pseudo may (do_prepare_recipe_sysroot) or may not (do_populate_sysroot_setscene) be running
+	# at this point so we're explicit about the environment so pseudo can load if
 	# not already present.
 	# PSEUDO_SYSROOT can contain references to the build architecture and COMPONENT_DIR
 	# so needs the STAGING_FIXME below
@@ -247,7 +247,7 @@ python __anonymous() {
 # (groupadd|useradd|usermod) parameters for all USERADD_PACKAGES in this recipe
 def get_all_cmd_params(d, cmd_type):
     import string
-    
+
     param_type = cmd_type.upper() + "_PARAM:%s"
     params = []
 


  parent reply	other threads:[~2026-08-13 19:16 UTC|newest]

Thread overview: 9+ 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 ` Jaipaul Cheernam [this message]
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 ` [OE-core] [PATCH 0/5] meta: fix trailing whitespace across classes, conf and recipes Mathieu Dubois-Briand
2026-08-15  9:45   ` Richard Purdie
2026-08-15 14:55     ` Jaipaul Cheernam

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=20260813191615.34122-4-jaipaul.cheernam@est.tech \
    --to=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.