From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com
Subject: [PATCH 0/7] raw2rgbpnm cleanups and a fix
Date: Tue, 17 Mar 2026 11:57:55 +0200 [thread overview]
Message-ID: <20260317095802.214532-1-sakari.ailus@linux.intel.com> (raw)
Hi folks,
Here are a few cleanups and fixes found in Laurent's review.
Sakari Ailus (7):
Reorder headers alphabetically
Check we have a supported format first before allocating memory
Add quotes for "-f help" in help text and do a line wrap
Constify progname
More header sorting
Use "stride" in a stride-related error message instead of an internal
name
Fix file size check
raw2rgbpnm.c | 47 +++++++++++++++++++++++++----------------------
1 file changed, 25 insertions(+), 22 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-17 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 9:57 Sakari Ailus [this message]
2026-03-17 9:57 ` [PATCH 1/7] Reorder headers alphabetically Sakari Ailus
2026-03-17 10:50 ` Laurent Pinchart
2026-03-17 9:57 ` [PATCH 2/7] Check we have a supported format first before allocating memory Sakari Ailus
2026-03-17 10:54 ` Laurent Pinchart
2026-03-17 13:11 ` Sakari Ailus
2026-03-17 9:57 ` [PATCH 3/7] Add quotes for "-f help" in help text and do a line wrap Sakari Ailus
2026-03-17 10:54 ` Laurent Pinchart
2026-03-17 9:57 ` [PATCH 4/7] Constify progname Sakari Ailus
2026-03-17 10:54 ` Laurent Pinchart
2026-03-17 9:58 ` [PATCH 5/7] More header sorting Sakari Ailus
2026-03-17 10:54 ` Laurent Pinchart
2026-03-17 9:58 ` [PATCH 6/7] Use "stride" in a stride-related error message instead of an internal name Sakari Ailus
2026-03-17 10:55 ` Laurent Pinchart
2026-03-17 9:58 ` [PATCH 7/7] Fix file size check Sakari Ailus
2026-03-17 10:57 ` Laurent Pinchart
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=20260317095802.214532-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox