From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mips@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 20
Date: Fri, 20 Nov 2020 14:41:23 +0100 [thread overview]
Message-ID: <20201120134123.GA10351@alpha.franken.de> (raw)
In-Reply-To: <CADVatmPzUv4zzzHJx23rFJgop1dHZrr7ReVoh48+Q5NAOkhzXA@mail.gmail.com>
On Fri, Nov 20, 2020 at 11:57:07AM +0000, Sudip Mukherjee wrote:
> Hi,
>
> On Fri, Nov 20, 2020 at 5:59 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > Changes since 20201119:
>
> mips allmodconfig fails for next-20201120 with the error:
> /home/sudip/linux/drivers/video/fbdev/udlfb.c: In function 'dlfb_ops_mmap':
> /home/sudip/linux/drivers/video/fbdev/udlfb.c:343:52: error:
> 'PAGE_SHARED' undeclared (first use in this function)
> 343 | if (remap_pfn_range(vma, start, page, PAGE_SIZE, PAGE_SHARED))
>
> Which has been caused by 0df162e1377a ("MIPS: mm: Clean up setup of
> protection map") which removed "PAGE_SHARED".
I'm working on it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-11-20 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 5:56 linux-next: Tree for Nov 20 Stephen Rothwell
2020-11-20 11:57 ` Sudip Mukherjee
2020-11-20 13:41 ` Thomas Bogendoerfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-20 6:07 Stephen Rothwell
2019-11-20 9:34 Stephen Rothwell
2019-11-20 11:22 ` Naresh Kamboju
2018-11-20 5:02 Stephen Rothwell
2017-11-20 3:45 Stephen Rothwell
2015-11-20 4:17 Stephen Rothwell
2014-11-20 7:46 Stephen Rothwell
2014-11-20 14:46 ` Guenter Roeck
2013-11-20 2:28 Stephen Rothwell
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=20201120134123.GA10351@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@gmail.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).