From: David Miller <davem@davemloft.net>
To: sowmini.varadhan@oracle.com
Cc: netdev@vger.kernel.org
Subject: Re: latest net-next does not build on sparc?
Date: Fri, 03 Jun 2016 19:20:48 -0400 (EDT) [thread overview]
Message-ID: <20160603.192048.1069869374683271001.davem@davemloft.net> (raw)
In-Reply-To: <20160603223925.GQ16616@oracle.com>
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Fri, 3 Jun 2016 18:39:25 -0400
> Just pulled 4.7.0-rc1, and I find a build error
>
> kernel/locking/rwsem.c: In function ?down_write_killable?:
> kernel/locking/rwsem.c:65: error: implicit declaration of function ?__down_write_killable?
> make[2]: *** [kernel/locking/rwsem.o] Error 1
>
> I had to pull in this patch:
> http://lkml.iu.edu/hypermail/linux/kernel/1602.3/04431.html
> to get it to build- did I just miss something in my pull?
That change isn't even in Linus's tree.
prev parent reply other threads:[~2016-06-03 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 22:39 latest net-next does not build on sparc? Sowmini Varadhan
2016-06-03 23:20 ` David Miller [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=20160603.192048.1069869374683271001.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).