Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/1] Add support for teamd/libteam
Date: Mon, 19 Jul 2021 11:38:14 +0200	[thread overview]
Message-ID: <20210719093815.2017764-1-troglobit@gmail.com> (raw)

Hi everyone!

Third time's a charm, I hope.  Here's the updated patch to add support
for teamd/libteam in Buildroot.  As mentioned previously, a few musl
libc related patches have been backported from project's master branch
at

    https://github.com/jpirko/libteam/

This time the Config.in dependency handling is actually fixed.  I did
not really understand it before.  Huge thanks to Yann and Yegor for
patiently explaining it to me!

I've also dropped the previously selected team modes, as suggested by
Yann, and rearranged the directives in libteam.mk slightly.  Could not
find any official CPE, so used the package name, as other packages do.

Basic tests still pass, and as of v3 br-arm-full-static is now skipped,
as expected:

    $ ./utils/check-package package/libteam/*
    199 lines processed
    0 warnings generated

    $ ./utils/test-pkg -c libteam.config -p libteam
               bootlin-armv5-uclibc [1/6]: OK
                bootlin-armv7-glibc [2/6]: OK
              bootlin-armv7m-uclibc [3/6]: SKIPPED
                bootlin-x86-64-musl [4/6]: OK
                 br-arm-full-static [5/6]: SKIPPED
                       sourcery-arm [6/6]: OK
    6 builds, 2 skipped, 0 build failed, 0 legal-info failed


Best regards
 /Joachim

Reviewed-by: Yann E. MORIN <yann.morin.1998@free.fr>
Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>

---
v3:
 - properly fix dependency handling
 - update package comment, depends on mmu
 - rearrange .mk slightly and add CPE vendor
 - update team kernel deps
 - drop team modes from kernel conf
 - update help with info on team modes
v2:
 - added missing libnl deps in libteam/Config.in

Joachim Wiberg (1):
  package/libteam: new package

 DEVELOPERS                                    |  1 +
 package/Config.in                             |  1 +
 .../0001-revert-disregard-current-state.patch | 51 +++++++++++++++++++
 .../0002-fix-build-on-openwrt-musl-libc.patch | 41 +++++++++++++++
 ...3-increase-wait-time-for-daemon-kill.patch | 37 ++++++++++++++
 package/libteam/Config.in                     | 30 +++++++++++
 package/libteam/libteam.hash                  |  3 ++
 package/libteam/libteam.mk                    | 24 +++++++++
 8 files changed, 188 insertions(+)
 create mode 100644 package/libteam/0001-revert-disregard-current-state.patch
 create mode 100644 package/libteam/0002-fix-build-on-openwrt-musl-libc.patch
 create mode 100644 package/libteam/0003-increase-wait-time-for-daemon-kill.patch
 create mode 100644 package/libteam/Config.in
 create mode 100644 package/libteam/libteam.hash
 create mode 100644 package/libteam/libteam.mk

-- 
2.25.1

             reply	other threads:[~2021-07-19  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  9:38 Joachim Wiberg [this message]
2021-07-19  9:38 ` [Buildroot] [PATCH v3 1/1] package/libteam: new package Joachim Wiberg
2021-11-05 21:05   ` Yann E. MORIN
2021-09-22 15:59 ` [Buildroot] [PATCH v3 0/1] Add support for teamd/libteam Joachim Wiberg

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=20210719093815.2017764-1-troglobit@gmail.com \
    --to=troglobit@gmail.com \
    --cc=buildroot@busybox.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