Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/2] package/edid-decode: bump version to 2d44e1b
Date: Thu, 4 May 2023 22:41:37 +0200	[thread overview]
Message-ID: <20230504204137.GA2661@scaer> (raw)
In-Reply-To: <20230504202137.18145-2-ps.report@gmx.net>

Peter, All,

On 2023-05-04 22:21 +0200, Peter Seiderer spake thusly:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

Both patches applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/edid-decode/edid-decode.hash | 2 +-
>  package/edid-decode/edid-decode.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/edid-decode/edid-decode.hash b/package/edid-decode/edid-decode.hash
> index 65d6c71079..8bece94911 100644
> --- a/package/edid-decode/edid-decode.hash
> +++ b/package/edid-decode/edid-decode.hash
> @@ -1,3 +1,3 @@
>  # Locally computed
> -sha256  c1a6222083c59f0499b3e43c159aee7e4c6c07d33b790d490a13fd62942fa9b5  edid-decode-188950472c19492547e298b27f9da0d72cf826df-br1.tar.gz
> +sha256  a8774f1d3eb031ffa4ecb85135b47ad28afeeaa7cf9e8410c5b51a29b83bbfdd  edid-decode-2d44e1b01c7ed7d65b20ecdce62d354841832201-br1.tar.gz
>  sha256  9bc7ab961e9a07dc84eaa0210af388def56d024357e79671fb89fe27d073eed7  LICENSE
> diff --git a/package/edid-decode/edid-decode.mk b/package/edid-decode/edid-decode.mk
> index 7e463c02b1..cd0bdfa0f0 100644
> --- a/package/edid-decode/edid-decode.mk
> +++ b/package/edid-decode/edid-decode.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -EDID_DECODE_VERSION = 188950472c19492547e298b27f9da0d72cf826df
> +EDID_DECODE_VERSION = 2d44e1b01c7ed7d65b20ecdce62d354841832201
>  EDID_DECODE_SITE = git://linuxtv.org/edid-decode.git
>  EDID_DECODE_LICENSE = MIT
>  EDID_DECODE_LICENSE_FILES = LICENSE
> -- 
> 2.40.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-05-04 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 20:21 [Buildroot] [PATCH v1 1/2] package/edid-decode: fix typo in Config.in for comment selection Peter Seiderer
2023-05-04 20:21 ` [Buildroot] [PATCH v1 2/2] package/edid-decode: bump version to 2d44e1b Peter Seiderer
2023-05-04 20:41   ` Yann E. MORIN [this message]
2023-05-16 12:36 ` [Buildroot] [PATCH v1 1/2] package/edid-decode: fix typo in Config.in for comment selection Peter Korsgaard

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=20230504204137.GA2661@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    /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