Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 2/2] utils/genrandconfig: don't build igh-ethercat drivers
Date: Sat, 26 Nov 2022 19:19:13 +0100	[thread overview]
Message-ID: <87lenxfuji.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221116212105.702408-2-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Wed, 16 Nov 2022 22:21:05 +0100")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > igh-ethercat comes with a small number of patched Linux kernel network
 > drivers, which aim at replacing the ones available in upstream Linux
 > kernel. All those drivers are provided only for specific kernel
 > releases. For example:

 > r8169-2.6.24-ethercat.c
 > r8169-2.6.24-orig.c
 > r8169-2.6.27-ethercat.c
 > r8169-2.6.27-orig.c
 > r8169-2.6.28-ethercat.c
 > r8169-2.6.28-orig.c
 > r8169-2.6.29-ethercat.c
 > r8169-2.6.29-orig.c
 > r8169-2.6.31-ethercat.c
 > r8169-2.6.31-orig.c
 > r8169-2.6.32-ethercat.c
 > r8169-2.6.32-orig.c
 > r8169-2.6.33-ethercat.c
 > r8169-2.6.33-orig.c
 > r8169-2.6.35-ethercat.c
 > r8169-2.6.35-orig.c
 > r8169-2.6.36-ethercat.c
 > r8169-2.6.36-orig.c
 > r8169-2.6.37-ethercat.c
 > r8169-2.6.37-orig.c
 > r8169-3.10-ethercat.c
 > r8169-3.10-orig.c
 > r8169-3.12-ethercat.c
 > r8169-3.12-orig.c
 > r8169-3.14-ethercat.c
 > r8169-3.14-orig.c
 > r8169-3.16-ethercat.c
 > r8169-3.16-orig.c
 > r8169-3.2-ethercat.c
 > r8169-3.2-orig.c
 > r8169-3.4-ethercat.c
 > r8169-3.4-orig.c
 > r8169-3.6-ethercat.c
 > r8169-3.6-orig.c
 > r8169-3.8-ethercat.c
 > r8169-3.8-orig.c
 > r8169-4.4-ethercat.c
 > r8169-4.4-orig.c

 > Obviously, this doesn't play well with the random configuration
 > testing done by utils/genrandconfig. This commit avoids this issue by
 > making sure we never build any of those drivers as part of the
 > genrandconfig generated configurations.

 > Fixes:

 >   http://autobuild.buildroot.net/results/07b7475d780c067d99ee5618a5fd2bb024a5b4e7/

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2022.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-26 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 21:21 [Buildroot] [PATCH 1/2] package/igh-ethercat: bump to latest Git commit Thomas Petazzoni via buildroot
2022-11-16 21:21 ` [Buildroot] [PATCH 2/2] utils/genrandconfig: don't build igh-ethercat drivers Thomas Petazzoni via buildroot
2022-11-26 18:19   ` Peter Korsgaard [this message]
2022-11-21 21:21 ` [Buildroot] [PATCH 1/2] package/igh-ethercat: bump to latest Git commit 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=87lenxfuji.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --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