From: Petr Vorel <petr.vorel@gmail.com> To: ltp@lists.linux.it Cc: Li Wang <liwang@redhat.com>, Martin Doucha <mdoucha@suse.cz>, Cyril Hrubis <chrubis@suse.cz>, buildroot@buildroot.org Subject: [Buildroot] [RFC PATCH v2 0/3] Fix old toolchain (< v3.14) Date: Thu, 30 Sep 2021 20:30:55 +0200 [thread overview] Message-ID: <20210930183058.5240-1-petr.vorel@gmail.com> (raw) Hi, NOTE: this fix (3rd commit) is needed obviously due very old toolchain (sourcery-arm from Buildroot). I suppose it's still used, but can anybody from Buildroot confirm this? Kind regards, Petr changes v1->v2: * fixing moving IFA_FLAGS from lapi/rtnetlink.h to lapi/if_addr.h (it was by accident done in 2 commits) * new commit tst_netdevice.c: Drop redundant include Petr Vorel (3): tst_netdevice.c: Drop redundant include lapi: Create if_addr.h and reuse it in rtnetlink.h lapi/if_addr.h: Define IFA_FLAGS include/lapi/if_addr.h | 19 +++++++++++++++++++ include/lapi/rtnetlink.h | 5 +---- lib/tst_netdevice.c | 1 - testcases/cve/icmp_rate_limit01.c | 3 ++- 4 files changed, 22 insertions(+), 6 deletions(-) create mode 100644 include/lapi/if_addr.h -- 2.33.0 _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <petr.vorel@gmail.com> To: ltp@lists.linux.it Cc: buildroot@buildroot.org Subject: [LTP] [RFC PATCH v2 0/3] Fix old toolchain (< v3.14) Date: Thu, 30 Sep 2021 20:30:55 +0200 [thread overview] Message-ID: <20210930183058.5240-1-petr.vorel@gmail.com> (raw) Hi, NOTE: this fix (3rd commit) is needed obviously due very old toolchain (sourcery-arm from Buildroot). I suppose it's still used, but can anybody from Buildroot confirm this? Kind regards, Petr changes v1->v2: * fixing moving IFA_FLAGS from lapi/rtnetlink.h to lapi/if_addr.h (it was by accident done in 2 commits) * new commit tst_netdevice.c: Drop redundant include Petr Vorel (3): tst_netdevice.c: Drop redundant include lapi: Create if_addr.h and reuse it in rtnetlink.h lapi/if_addr.h: Define IFA_FLAGS include/lapi/if_addr.h | 19 +++++++++++++++++++ include/lapi/rtnetlink.h | 5 +---- lib/tst_netdevice.c | 1 - testcases/cve/icmp_rate_limit01.c | 3 ++- 4 files changed, 22 insertions(+), 6 deletions(-) create mode 100644 include/lapi/if_addr.h -- 2.33.0 -- Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2021-09-30 18:31 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-30 18:30 Petr Vorel [this message] 2021-09-30 18:30 ` [LTP] [RFC PATCH v2 0/3] Fix old toolchain (< v3.14) Petr Vorel 2021-09-30 18:30 ` [Buildroot] [RFC PATCH v2 1/3] tst_netdevice.c: Drop redundant include Petr Vorel 2021-09-30 18:30 ` [LTP] " Petr Vorel 2021-10-06 13:51 ` Cyril Hrubis 2021-09-30 18:30 ` [Buildroot] [RFC PATCH v2 2/3] lapi: Create if_addr.h and reuse it in rtnetlink.h Petr Vorel 2021-09-30 18:30 ` [LTP] " Petr Vorel 2021-10-06 13:52 ` Cyril Hrubis 2021-09-30 18:30 ` [Buildroot] [RFC PATCH v2 3/3] lapi/if_addr.h: Define IFA_FLAGS Petr Vorel 2021-09-30 18:30 ` [LTP] " Petr Vorel 2021-10-01 9:19 ` Martin Doucha 2021-10-02 17:23 ` Petr Vorel 2021-10-06 14:00 ` Cyril Hrubis 2021-10-06 19:08 ` [Buildroot] " Petr Vorel 2021-10-06 19:08 ` [LTP] " Petr Vorel
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=20210930183058.5240-1-petr.vorel@gmail.com \ --to=petr.vorel@gmail.com \ --cc=buildroot@buildroot.org \ --cc=chrubis@suse.cz \ --cc=liwang@redhat.com \ --cc=ltp@lists.linux.it \ --cc=mdoucha@suse.cz \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.