From: Peter Robinson <pbrobinson@gmail.com>
To: linux-firmware@kernel.org
Cc: jwboyer@kernel.org, Peter Robinson <pbrobinson@gmail.com>
Subject: [RFC] cpia2: add EOL entry for firmware
Date: Fri, 19 Jan 2024 11:28:16 +0000 [thread overview]
Message-ID: <20240119112816.527360-1-pbrobinson@gmail.com> (raw)
The cpia2 driver was removed from the v6.3 kernel so add an
EOL entry to WHENCE do we can track this so the FW can be
removed when the v6.1 LTS kernel goes EOL.
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
---
Seeking a way to document this upstream so it can be tracked
in a central location so I'd like feedback if this would be
a reasonable way to track this information?
WHENCE | 1 +
1 file changed, 1 insertion(+)
diff --git a/WHENCE b/WHENCE
index 9db8b41f..446067b1 100644
--- a/WHENCE
+++ b/WHENCE
@@ -274,6 +274,7 @@ Converted from Intel HEX files, used in our binary representation of ihex.
--------------------------------------------------------------------------
Driver: cpia2 -- cameras based on Vision's CPiA2
+EOL: v6.3
File: cpia2/stv0672_vp4.bin
--
2.43.0
reply other threads:[~2024-01-19 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240119112816.527360-1-pbrobinson@gmail.com \
--to=pbrobinson@gmail.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).