The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>,
	linux-kernel@vger.kernel.org
Cc: jgg@ziepe.ca, Liam.Howlett@Oracle.com, david@redhat.com,
	willy@infradead.org, akpm@linux-foundation.org,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [RFC PATCH v1 0/1] possibile regression in the mm_types
Date: Sun, 12 Mar 2023 17:45:11 -0700	[thread overview]
Message-ID: <a5f8ae02-85f5-b98a-5900-603f189ccb85@nvidia.com> (raw)
In-Reply-To: <20230312224150.425382-1-vincenzopalazzodev@gmail.com>

On 3/12/23 15:41, Vincenzo Palazzo wrote:
> While I was testing the last rc1 version on my build machine
> I noticed that I was not able to build my nvidia driver and 
> also, the vboxhost/7.0.6_OSE driver while I was building [1].
> 
> So I noticed that this change was introduced in the 6.3-rc1 
> and proposed by [2]. However, I think I can miss important 
> around this change,  there may be some motivation to 
> have the `const` constraint here, 
> and this change needs to be done in the out-of-tree driver 

Yes it does. The out of tree drivers are responsible for keeping
themselves up to date.

Note also that this is an -rc kernel. NVIDIA is generally careful 
to keep its driver building against released kernels, but with -rc
kernels we often just wait until the kernel is released, in order
to avoid too much churn. Most customers don't (and shouldn't) run
an -rc Linux kernel anyway, is why.

Anyway, no, we don't patch the upstream kernel for this kind of 
issue. But thanks for thinking about it. :)

thanks,
-- 
John Hubbard
NVIDIA

      reply	other threads:[~2023-03-13  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 22:41 [RFC PATCH v1 0/1] possibile regression in the mm_types Vincenzo Palazzo
2023-03-13  0:45 ` John Hubbard [this message]

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=a5f8ae02-85f5-b98a-5900-603f189ccb85@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=Liam.Howlett@Oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincenzopalazzodev@gmail.com \
    --cc=willy@infradead.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