treewide: bulk update patches with status field

While the insane.bbclass upstream-status check hasn't been made
default, users of meta-virtualization may have it enabled in their
distros .. so the effect is the same. We must have this tracking
tag in out patches.

This is a bulk update to add the tag and silence the QA message.

As packages get updated, the normal/routine process of checking
the patches will continue, and the status fields may (or may not)
get more useful.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

1 files changed, 3 insertions, 1 deletions

diff --git a/recipes-devtools/go/go-build/0001-build-use-instead-of-go.patch b/recipes-devtools/go/go-build/0001-build-use-instead-of-go.patch
index 6d6b0af4..eb634f3d 100644
--- a/recipes-devtools/go/go-build/0001-build-use-instead-of-go.patch
+++ b/recipes-devtools/go/go-build/0001-build-use-instead-of-go.patch
@@ -1,11 +1,13 @@
 From 4db28c98481056c41097f808335c37e8517fe485 Mon Sep 17 00:00:00 2001
 From: Bruce Ashfield <bruce.ashfield@gmail.com>
 Date: Fri, 7 Aug 2020 23:39:18 -0400
-Subject: [PATCH] build: use  instead of 'go'
+Subject: [PATCH] build: use ${GO} instead of 'go'
 
 While we can get away with 'go' if the host/target arch match, the
 new go-binary toolchain blows up in a cross compile situation.
 
+Upstream-Status: Inappropriate [embedded specific]
+
 Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
 ---
  gobuild/Makefile | 4 ++--