rtc-tools: Bump the recipe

From: Fabio Estevam <festevam@denx.de>

The patch that adds the rtc-tools Makefile has been accepted
upstream, so bump to the latest version and remove the local
Makefile patch.

Signed-off-by: Fabio Estevam <festevam@denx.de>
---
 .../0001-rtc-tools-Add-a-Makefile.patch       | 39 -------------------
 .../rtc-tools/rtc-tools_1.0.0.bb              |  6 +--
 2 files changed, 2 insertions(+), 43 deletions(-)
 delete mode 100644 meta-oe/recipes-support/rtc-tools/rtc-tools/0001-rtc-tools-Add-a-Makefile.patch

> -----Original Message-----
> From: openembedded-devel@lists.openembedded.org <openembedded-devel@lists.openembedded.org> On Behalf Of Fabio Estevam
> Sent: den 16 februari 2022 15:14
> To: openembedded-devel@lists.openembedded.org
> Cc: raj.khem@gmail.com; Fabio Estevam <festevam@denx.de>
> Subject: [oe] [PATCH] rtc-tools: Bump the recipe

I suggest changing the Git subject to:

rtc-tools: Update to 2022.02

as that is what the change is tagged as (also see below).

> 
> From: Fabio Estevam <festevam@denx.de>
> 
> The patch that adds the rtc-tools Makefile has been accepted
> upstream, so bump to the latest version and remove the local
> Makefile patch.
> 
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
>  .../0001-rtc-tools-Add-a-Makefile.patch       | 39 -------------------
>  .../rtc-tools/rtc-tools_1.0.0.bb              |  6 +--
>  2 files changed, 2 insertions(+), 43 deletions(-)
>  delete mode 100644 meta-oe/recipes-support/rtc-tools/rtc-tools/0001-rtc-tools-Add-a-Makefile.patch
> 
> diff --git a/meta-oe/recipes-support/rtc-tools/rtc-tools/0001-rtc-tools-Add-a-Makefile.patch b/meta-oe/recipes-support/rtc-tools/rtc-tools/0001-rtc-tools-Add-a-Makefile.patch
> deleted file mode 100644
> index 1d16a66088e8..000000000000
> --- a/meta-oe/recipes-support/rtc-tools/rtc-tools/0001-rtc-tools-Add-a-Makefile.patch
> +++ /dev/null
> @@ -1,39 +0,0 @@
> -From 3e9dfc0f21191bdb3ab719479e9c1997a61c5044 Mon Sep 17 00:00:00 2001
> -From: Fabio Estevam <festevam@denx.de>
> -Date: Fri, 28 Jan 2022 13:34:45 -0300
> -Subject: [PATCH] rtc-tools: Add a Makefile
> -
> -Add a Makefile to make installation and uninstallation
> -process easier.
> -
> -Upstream-Status: Submitted [https://marc.info/?l=linux-
> rtc&m=164332426030004&w=2]
> -Signed-off-by: Fabio Estevam <festevam@denx.de>
> ----
> - Makefile | 16 ++++++++++++++++
> - 1 file changed, 16 insertions(+)
> - create mode 100644 Makefile
> -
> -diff --git a/Makefile b/Makefile
> -new file mode 100644
> -index 0000000..71a4c9c
> ---- /dev/null
> -+++ b/Makefile
> -@@ -0,0 +1,16 @@
> -+prefix ?= /usr
> -+bindir ?= $(prefix)/bin
> -+
> -+EXEC = rtc-range rtc rtc-sync
> -+
> -+all: $(EXEC)
> -+
> -+clean:
> -+	$(RM) $(EXEC)
> -+
> -+install:
> -+	install -d $(DESTDIR)$(bindir)
> -+	install $(EXEC) $(DESTDIR)$(bindir)
> -+
> -+uninstall:
> -+	$(RM) -r $(addprefix $(DESTDIR)$(bindir)/,$(EXEC))
> ---
> -2.25.1
> diff --git a/meta-oe/recipes-support/rtc-tools/rtc-tools_1.0.0.bb b/meta-oe/recipes-support/rtc-tools/rtc-tools_1.0.0.bb
> index 303585a6591d..d65f5da859af 100644
> --- a/meta-oe/recipes-support/rtc-tools/rtc-tools_1.0.0.bb
> +++ b/meta-oe/recipes-support/rtc-tools/rtc-tools_1.0.0.bb

It seems this was tagged as "2022.02" so the recipe should be 
renamed to "rtc-tools_2022.02.bb" to match.

> @@ -2,10 +2,8 @@ SUMMARY = "Useful programs to test rtc drivers"
>  LICENSE = "GPL-2.0-only"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=74274e8a218423e49eefdea80bc55038"
> 
> -SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/${BPN}.git;protocol=https;branch=master \
> -           file://0001-rtc-tools-Add-a-Makefile.patch \
> -           "
> -SRCREV = "acc442e7af4e1e783432a43d37f1a7938c692659"
> +SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/${BPN}.git;protocol=https;branch=master"
> +SRCREV = "61839777afedcc7bdb68ea4628c5ce5ca72c2ac8"
> 
>  S = "${WORKDIR}/git"
> 
> --
> 2.25.1

Hi Peter,

On Wed, Feb 16, 2022 at 1:49 PM Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:

> I suggest changing the Git subject to:
>
> rtc-tools: Update to 2022.02
>
> as that is what the change is tagged as (also see below).

Good catch! I did as you suggested and submitted a v2.

Thanks