Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kris Bahnsen via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	 buildroot@buildroot.org
Cc: Louis Aussedat <aussedat.louis@gmail.com>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Sergey Matyukevich <geomatsi@gmail.com>
Subject: Re: [Buildroot] [PATCH 7/7] package/wilc-driver: disable package for s390x architecture
Date: Wed, 26 Oct 2022 10:32:28 -0700	[thread overview]
Message-ID: <1666805548.3174.1.camel@embeddedTS.com> (raw)
In-Reply-To: <20221026132634.999254-8-giulio.benetti@benettiengineering.com>

On Wed, 2022-10-26 at 15:26 +0200, Giulio Benetti wrote:
> s390x doesn't support CONFIG_WIRELESS in Linux so let's disable this
> package for this architecture.
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  package/wilc-driver/Config.in | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/package/wilc-driver/Config.in b/package/wilc-driver/Config.in
> index 7ed062bb66..7f970bd38b 100644
> --- a/package/wilc-driver/Config.in
> +++ b/package/wilc-driver/Config.in
> @@ -1,5 +1,6 @@
>  config BR2_PACKAGE_WILC_DRIVER
>  	bool "wilc kernel module"
> +	depends on !BR2_s390x
>  	depends on BR2_LINUX_KERNEL
>  	help
>  	  External kernel module for WILC1000/3000 devices.
> @@ -59,4 +60,5 @@ endif
>  endif
>  
>  comment "wilc kernel module needs a Linux kernel to be built"
> +	depends on !BR2_s390x
>  	depends on !BR2_LINUX_KERNEL

I don't know much on the s390x arch, nor Buildroot paradigms for disabling packages
per-architecture, however the change itself looks good to me.

Reviewed-by: Kris Bahnsen <kris@embeddedTS.com>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-10-26 17:32 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 [this message]
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 ` [Buildroot] [PATCH 0/7] Disable packages with CONFIG_WIRELESS on s390x Thomas Petazzoni via buildroot

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=1666805548.3174.1.camel@embeddedTS.com \
    --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 \
    /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