Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14856] nvidia-driver package fails to build
Date: Mon, 20 Jun 2022 14:17:04 +0000	[thread overview]
Message-ID: <bug-14856-163-XCrciTkmZ9@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14856-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14856

--- Comment #3 from Vincent Fazio <vfazio@xes-inc.com> ---
Pretty sure the CC error may be addressed by
https://patchwork.ozlabs.org/project/buildroot/patch/20211104141910.1840914-1-vfazio@xes-inc.com/

version 390.151 has been released which adds support up to 5.17rc, the 390.132
package I think only technically supports through 5.4

I can resubmit my patch with the version bump and kick off a build to make sure
it at least compiles OK but I don't have the bandwidth to do actual hardware
testing at the moment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-06-20 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  9:03 [Buildroot] [Bug 14856] New: nvidia-driver package fails to build bugzilla
2022-06-20  9:16 ` [Buildroot] [Bug 14856] " bugzilla
2022-06-20 13:47 ` bugzilla
2022-06-20 14:17 ` bugzilla [this message]
2022-06-20 17:32 ` bugzilla
2022-06-21  7:30 ` bugzilla
2022-06-21  8:43 ` bugzilla
2022-06-21 12:02 ` bugzilla
2022-06-21 12:43 ` bugzilla
2024-06-15 15:03 ` bugzilla

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=bug-14856-163-XCrciTkmZ9@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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