Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Gregory Dymarek <gregd72002@gmail.com>,
	Thomas Devoogdt <thomas.devoogdt@barco.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/libsrtp: bump to version 2.5.0
Date: Sat, 2 Sep 2023 09:47:13 +0200	[thread overview]
Message-ID: <20230902094713.0e42841d@windsurf> (raw)
In-Reply-To: <20230830080013.1862029-1-thomas.devoogdt@barco.com>

On Wed, 30 Aug 2023 10:00:13 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:

> https://github.com/cisco/libsrtp/releases/tag/v2.5.0
> 
> See detailed change log:
> https://github.com/cisco/libsrtp/blob/v2.5.0/CHANGES#L3-L43
> 
> Dropped patch wich was already upstream.
> 
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
> ---
> v2: update .checkpackageignore
> ---
>  .checkpackageignore                           |  1 -
>  ...legacy-OpenSSL-to-fix-LibreSSL-build.patch | 86 -------------------
>  package/libsrtp/libsrtp.hash                  |  2 +-
>  package/libsrtp/libsrtp.mk                    |  2 +-
>  4 files changed, 2 insertions(+), 89 deletions(-)
>  delete mode 100644 package/libsrtp/0001-Remove-compatibility-code-for-legacy-OpenSSL-to-fix-LibreSSL-build.patch

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-09-02  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  8:00 [Buildroot] [PATCH v2] package/libsrtp: bump to version 2.5.0 Thomas Devoogdt
2023-09-02  7:47 ` Thomas Petazzoni via buildroot [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=20230902094713.0e42841d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=gregd72002@gmail.com \
    --cc=thomas.devoogdt@barco.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.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