From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kris Bahnsen via buildroot <buildroot@buildroot.org>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
kris@embeddedTS.com
Subject: Re: [Buildroot] [PATCH] package/wilc-driver: bump version to 2024.04
Date: Mon, 15 Jul 2024 21:24:42 +0200 [thread overview]
Message-ID: <20240715212442.367a9df9@windsurf> (raw)
In-Reply-To: <27d046a7a40bbc72279aac3e5971d8d58842b55d.camel@embeddedTS.com>
On Mon, 15 Jul 2024 11:25:13 -0700
Kris Bahnsen via buildroot <buildroot@buildroot.org> wrote:
> Be advised that this does NOT support "up to" Linux 6.6. The latest
> updates from Microchip drop any backwards compatibility support, which
> is why we have not pushed this up to Buildroot yet.
>
> I think this only will support kernels 6.2~6.6 and currently do not
> believe it will compile against upstream Linux 6.9 (I tested it a while
> ago but don't remember the outcome as it wasn't important).
>
> As I mentioned in my previous email responding to build failures, we're
> working on a solution to be able to handle backwards compatibility with
> 'backports' but are first catching up on other tasks.
So what can we do in the mean time? Support a few versions of the
driver, and let the user chose?
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
next prev parent reply other threads:[~2024-07-15 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 18:02 [Buildroot] [PATCH] package/wilc-driver: bump version to 2024.04 Giulio Benetti
2024-07-15 18:25 ` Kris Bahnsen via buildroot
2024-07-15 18:54 ` Giulio Benetti
2024-07-15 19:24 ` Thomas Petazzoni via buildroot [this message]
2024-07-15 20:11 ` Kris Bahnsen 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=20240715212442.367a9df9@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 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.