From: Ryan Eatmon <reatmon@ti.com>
To: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
<meta-ti@lists.yoctoproject.org>
Subject: [meta-ti][master][PATCH] gdbc6x: Fix Upstream-Status tag
Date: Thu, 8 Feb 2024 12:54:46 -0600 [thread overview]
Message-ID: <20240208185446.1999-2-reatmon@ti.com> (raw)
In-Reply-To: <20240208185446.1999-1-reatmon@ti.com>
We should be using Inactive-Upstream instead of Pending for these
patches.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
.../0001-Support-Linux-kernels-v5.15.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-extras/recipes-devtools/gdbc6x/gdbserverproxy-module-drv/0001-Support-Linux-kernels-v5.15.patch b/meta-ti-extras/recipes-devtools/gdbc6x/gdbserverproxy-module-drv/0001-Support-Linux-kernels-v5.15.patch
index cb56a470..fdf7e95f 100644
--- a/meta-ti-extras/recipes-devtools/gdbc6x/gdbserverproxy-module-drv/0001-Support-Linux-kernels-v5.15.patch
+++ b/meta-ti-extras/recipes-devtools/gdbc6x/gdbserverproxy-module-drv/0001-Support-Linux-kernels-v5.15.patch
@@ -8,7 +8,7 @@ put_tty_driver was removed and write_room return type has changed.
Function tty_driver_kref_put has been around a while, so no need
to do a kernel version check.
-Upstream-Status: Pending
+Upstream-Status: Inactive-Upstream
Signed-off-by: Andrew Davis <afd@ti.com>
---
kernel_module/gdbproxy-mod/gdbserverproxy.c | 6 +++++-
--
2.17.1
prev parent reply other threads:[~2024-02-08 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 18:54 [meta-ti][master][PATCH v2] gdbc6x: Fix kernel module to work on 6.6+ Ryan Eatmon
2024-02-08 18:54 ` Ryan Eatmon [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=20240208185446.1999-2-reatmon@ti.com \
--to=reatmon@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).