From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Louis Aussedat <aussedat.louis@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Kris Bahnsen <kris@embeddedTS.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/7] Disable packages with CONFIG_WIRELESS on s390x
Date: Wed, 26 Oct 2022 21:53:24 +0200 [thread overview]
Message-ID: <20221026215324.63c63c41@windsurf> (raw)
In-Reply-To: <20221026132634.999254-1-giulio.benetti@benettiengineering.com>
On Wed, 26 Oct 2022 15:26:27 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Linux s390x doesn't support CONFIG_WIRELESS so this patchset disable
> all packages with Linux CONFIG_WIRELESS for s390x architecture.
>
> Giulio Benetti (7):
> package/rtl8189es: disable package for s390x architecture
> package/rtl8189fs: disable package for s390x architecture
> package/rtl8723bu: disable package for s390x architecture
> package/rtl8723ds: disable package for s390x architecture
> package/rtl8812au-aircrack-ng: disable package for s390x architecture
> package/rtl8821au: disable package for s390x architecture
> package/wilc-driver: disable package for s390x architecture
When I saw this, initially I was a bit "meh", and wondered if some more
generic mechanism wouldn't be more relevant, like a
BR2_LINUX_KERNEL_SUPPORTS_WIRELESS or something like this. But then I
thought that this is the first case for which we have a situation like
that, so we're not sure what other cases will look like.
So for now, I applied your patches as-is, and we can revisit later if
we identify similar issues that would encourage us in finding a more
generic solution to the problem.
So: all patches applied as-is. Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-10-26 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 13:26 [Buildroot] [PATCH 0/7] Disable packages with CONFIG_WIRELESS on s390x Giulio Benetti
2022-10-26 13:26 ` [Buildroot] [PATCH 1/7] package/rtl8189es: disable package for s390x architecture Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 13:26 ` [Buildroot] [PATCH 2/7] package/rtl8189fs: " Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 13:26 ` [Buildroot] [PATCH 3/7] package/rtl8723bu: " Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 13:26 ` [Buildroot] [PATCH 4/7] package/rtl8723ds: " Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 13:26 ` [Buildroot] [PATCH 5/7] package/rtl8812au-aircrack-ng: " Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 13:26 ` [Buildroot] [PATCH 6/7] package/rtl8821au: " Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 13:26 ` [Buildroot] [PATCH 7/7] package/wilc-driver: " Giulio Benetti
2022-10-26 17:32 ` Kris Bahnsen via buildroot
2022-10-26 17:53 ` Giulio Benetti
2022-10-26 18:11 ` Giulio Benetti
2022-11-06 10:04 ` Peter Korsgaard
2022-10-26 19:53 ` 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=20221026215324.63c63c41@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=aussedat.louis@gmail.com \
--cc=geomatsi@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=kris@embeddedTS.com \
--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 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.