From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/ocf-linux: remove package
Date: Tue, 11 Jul 2023 23:48:31 +0200 [thread overview]
Message-ID: <20230711234831.27f0b988@windsurf> (raw)
In-Reply-To: <20230706191912.3008144-1-bernd@kuhls.net>
On Thu, 6 Jul 2023 21:19:11 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/88b/88b5d14b315af1669fff04f8c11c321cc4c107c7/
>
> The package seems to be unmainted, asking for support of kernels >= 5.6
> a year ago was unanswered:
> https://sourceforge.net/p/ocf-linux/mailman/message/37662698/
>
> This patch follow Thomas' suggestion to remove the package:
> https://lists.buildroot.org/pipermail/buildroot/2022-November/654688.html
>
> Remove the virtual package cryptodev which is not needed anymore.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> Config.in.legacy | 14 ++++++
> package/Config.in | 2 +-
> package/cryptodev-linux/Config.in | 14 ++++++
> package/cryptodev-linux/cryptodev-linux.mk | 2 -
> package/cryptodev/Config.in | 50 ----------------------
> package/cryptodev/cryptodev.mk | 7 ---
> package/libopenssl/libopenssl.mk | 6 +--
> package/ocf-linux/ocf-linux.hash | 2 -
> package/ocf-linux/ocf-linux.mk | 26 -----------
> package/openswan/openswan.mk | 3 --
> 10 files changed, 32 insertions(+), 94 deletions(-)
> create mode 100644 package/cryptodev-linux/Config.in
> delete mode 100644 package/cryptodev/Config.in
> delete mode 100644 package/cryptodev/cryptodev.mk
> delete mode 100644 package/ocf-linux/ocf-linux.hash
> delete mode 100644 package/ocf-linux/ocf-linux.mk
Thanks, both patches applied!
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
prev parent reply other threads:[~2023-07-11 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 19:19 [Buildroot] [PATCH 1/2] package/ocf-linux: remove package Bernd Kuhls
2023-07-06 19:19 ` [Buildroot] [PATCH 2/2] package/cryptodev-linux: bump version to 1.13 Bernd Kuhls
2023-08-25 14:39 ` Peter Korsgaard
2023-07-06 20:13 ` [Buildroot] [PATCH 1/2] package/ocf-linux: remove package Arnout Vandecappelle via buildroot
2023-07-11 21:48 ` 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=20230711234831.27f0b988@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.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