Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org, Kris Bahnsen <kris@embeddedTS.com>
Subject: Re: [Buildroot] [PATCH] package/wilc-driver: fix build failure with Linux 6.10
Date: Sat, 19 Apr 2025 16:34:17 +0200	[thread overview]
Message-ID: <20250419163417.6a103c75@windsurf> (raw)
In-Reply-To: <20250417171339.3718898-1-giulio.benetti@benettiengineering.com>

On Thu, 17 Apr 2025 19:13:39 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> Add local patches pending upstream to fix 3 different API changes
> throughout Linux 6.7, 6.8, 6.10.
> 
> Fixes:
> https://autobuild.buildroot.org/results/e001f70dab4c9cebdbde0443f4f8bb6b42ae5561/
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  .../0008-Fix-build-with-Linux-6.7.patch       | 46 ++++++++++++++++
>  .../0009-Fix-build-with-Linux-6.8.patch       | 34 ++++++++++++
>  .../0010-Fix-build-with-Linux-6.10.patch      | 55 +++++++++++++++++++
>  3 files changed, 135 insertions(+)
>  create mode 100644 package/wilc-driver/0008-Fix-build-with-Linux-6.7.patch
>  create mode 100644 package/wilc-driver/0009-Fix-build-with-Linux-6.8.patch
>  create mode 100644 package/wilc-driver/0010-Fix-build-with-Linux-6.10.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-04-19 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 17:13 [Buildroot] [PATCH] package/wilc-driver: fix build failure with Linux 6.10 Giulio Benetti
2025-04-19 14:34 ` Thomas Petazzoni via buildroot [this message]
2025-05-02 10:36 ` Arnout Vandecappelle 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=20250419163417.6a103c75@windsurf \
    --to=buildroot@buildroot.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox