public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-drivers/nvidia-drivers/files/
Date: Mon, 19 Sep 2022 11:36:52 +0000 (UTC)	[thread overview]
Message-ID: <1663587384.80a2da5a5eaad522ff3e8019d8584ed1e5420501.ionen@gentoo> (raw)

commit:     80a2da5a5eaad522ff3e8019d8584ed1e5420501
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 19 10:35:21 2022 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Mon Sep 19 11:36:24 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=80a2da5a

x11-drivers/nvidia-drivers: clarify clang15 patch notes

That this still fails regardless of 15.0.0-r1/15.0.1 revert
may not have been clear, this is the makefiles requesting it.

Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 x11-drivers/nvidia-drivers/files/nvidia-drivers-390.154-clang15.patch   | 2 ++
 .../nvidia-drivers/files/nvidia-drivers-470.141.03-clang15.patch        | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/x11-drivers/nvidia-drivers/files/nvidia-drivers-390.154-clang15.patch b/x11-drivers/nvidia-drivers/files/nvidia-drivers-390.154-clang15.patch
index 85d502ca662f..525631f36b3c 100644
--- a/x11-drivers/nvidia-drivers/files/nvidia-drivers-390.154-clang15.patch
+++ b/x11-drivers/nvidia-drivers/files/nvidia-drivers-390.154-clang15.patch
@@ -1,3 +1,5 @@
+Kernel's makefiles pass -Werror=strict-prototypes which
+trigger errors with clang15+
 https://bugs.gentoo.org/870238
 --- a/kernel/nvidia/nvlink_linux.c
 +++ b/kernel/nvidia/nvlink_linux.c

diff --git a/x11-drivers/nvidia-drivers/files/nvidia-drivers-470.141.03-clang15.patch b/x11-drivers/nvidia-drivers/files/nvidia-drivers-470.141.03-clang15.patch
index 71cb6cf7e980..ab88f2b997c3 100644
--- a/x11-drivers/nvidia-drivers/files/nvidia-drivers-470.141.03-clang15.patch
+++ b/x11-drivers/nvidia-drivers/files/nvidia-drivers-470.141.03-clang15.patch
@@ -1,3 +1,5 @@
+Kernel's makefiles pass -Werror=strict-prototypes which
+trigger errors with clang15+
 https://bugs.gentoo.org/870238
 --- a/kernel/nvidia/nvlink_linux.c
 +++ b/kernel/nvidia/nvlink_linux.c


             reply	other threads:[~2022-09-19 11:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 11:36 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-25 13:18 [gentoo-commits] repo/gentoo:master commit in: x11-drivers/nvidia-drivers/files/ Ionen Wolkens
2024-05-27  5:55 Ionen Wolkens
2024-01-28 16:34 Ionen Wolkens
2023-10-20  1:15 Ionen Wolkens
2023-06-18  2:03 Ionen Wolkens
2022-12-11 19:23 Ionen Wolkens
2022-11-10 22:22 Ionen Wolkens
2022-05-31 16:30 Ionen Wolkens
2021-08-21  5:33 Ionen Wolkens
2021-03-21 15:53 David Seifert
2021-03-21 15:53 David Seifert
2021-02-27 15:38 Conrad Kostecki
2020-09-17 20:29 Jeroen Roovers
2017-05-06 11:48 Jeroen Roovers
2017-01-24 12:21 Jeroen Roovers
2017-01-20  8:07 Jeroen Roovers
2016-05-18  6:42 Austin English

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=1663587384.80a2da5a5eaad522ff3e8019d8584ed1e5420501.ionen@gentoo \
    --to=ionen@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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