public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4.14.9 broke nvidia 384.98 kernel module
Date: Sat, 30 Dec 2017 15:18:23 +0100	[thread overview]
Message-ID: <20171230141823.GA9933@kroah.com> (raw)
In-Reply-To: <3907598.31jH6naT2q@xrated>

On Sat, Dec 30, 2017 at 01:36:33PM +0100, Hans-Peter Jansen wrote:
> On Freitag, 29. Dezember 2017 10:23:56 Greg KH wrote:
> > On Fri, Dec 29, 2017 at 02:08:08AM +0100, Hans-Peter Jansen wrote:
> > > Hi Greg,
> > > 
> > > I know, everybody hates NVidia and their proprietary stuff around here.
> > > 
> > > Anyway, I wanted to let you and followers of 4.14 know, that changes
> > > between> 
> > > 4.14.8 and 4.14.9 broke both current nvidia kernel drivers. See:
> > > 	https://devtalk.nvidia.com/default/topic/1028016/linux/patch-for-compilin
> > > 	g-v384-98-modules-with-linux-v4-14-9-/
> > Should be fixed in 4.14.10-rc1, right?
> 
> Hmm, building with 4.14.10 without the patch results in:
> 
> [   19s] + make -f Makefile nv-linux.o SYSSRC=/lib/modules/4.14.10-3-
> default/source SYSOUT=/usr/src/linux-obj/x86_64/default
> [...]
> [   88s] /home/abuild/rpmbuild/BUILD/nvidia-
> gfxG04-384.98/obj/default/384.98/nvidia-uvm/uvm8_va_block.c:8771:41: error: 
> implicit declaration of function 'task_stack_page' [-Werror=implicit-function-
> declaration]
> 
> With the patch applied (attached for reference), the build succeeds..

That's not an issue I can do anything about, that's an nvidia driver
problem :)

thanks,

greg k-h

      reply	other threads:[~2017-12-30 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29  1:08 4.14.9 broke nvidia 384.98 kernel module Hans-Peter Jansen
2017-12-29  9:23 ` Greg KH
2017-12-30 12:36   ` Hans-Peter Jansen
2017-12-30 14:18     ` Greg KH [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=20171230141823.GA9933@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.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