linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: Joe Perches <joe@perches.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"pali@kernel.org" <pali@kernel.org>,
	"dsterba@suse.cz" <dsterba@suse.cz>,
	"aaptel@suse.com" <aaptel@suse.com>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"mark@harmstone.com" <mark@harmstone.com>,
	"nborisov@suse.com" <nborisov@suse.com>
Subject: Re: [PATCH v5 03/10] fs/ntfs3: Add bitmap
Date: Fri, 18 Sep 2020 17:38:14 +0100	[thread overview]
Message-ID: <20200918163814.GF32101@casper.infradead.org> (raw)
In-Reply-To: <5b2fbfee0a9d4ee59c0e624844560413@paragon-software.com>

On Fri, Sep 18, 2020 at 04:29:34PM +0000, Konstantin Komarov wrote:
> From: Joe Perches <joe@perches.com>
> Sent: Sunday, September 13, 2020 9:44 PM
> > 
> > On Fri, 2020-09-11 at 17:10 +0300, Konstantin Komarov wrote:
> > > This adds bitmap
> > 
> > $ make fs/ntfs3/
> >   SYNC    include/config/auto.conf.cmd
> >   CALL    scripts/checksyscalls.sh
> >   CALL    scripts/atomic/check-atomics.sh
> >   DESCEND  objtool
> >   CC      fs/ntfs3/bitfunc.o
> >   CC      fs/ntfs3/bitmap.o
> > fs/ntfs3/bitmap.c: In function ‘wnd_rescan’:
> > fs/ntfs3/bitmap.c:556:4: error: implicit declaration of function ‘page_cache_readahead_unbounded’; did you mean
> > ‘page_cache_ra_unbounded’? [-Werror=implicit-function-declaration]
> >   556 |    page_cache_readahead_unbounded(
> >       |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >       |    page_cache_ra_unbounded
> > cc1: some warnings being treated as errors
> > make[2]: *** [scripts/Makefile.build:283: fs/ntfs3/bitmap.o] Error 1
> > make[1]: *** [scripts/Makefile.build:500: fs/ntfs3] Error 2
> > make: *** [Makefile:1792: fs] Error 2
> > 
> Hi Joe! Doesn't seem to be an issue for 5.9_rc5. Which repo should've
> been used to reproduce?

It's in the -mm tree, which is included in linux-next.

  reply	other threads:[~2020-09-18 16:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 14:10 [PATCH v5 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2020-09-12  2:28   ` Joe Perches
2020-09-11 14:10 ` [PATCH v5 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2020-09-13 18:43   ` Joe Perches
2020-09-14  2:38     ` Matthew Wilcox
2020-09-18 16:35       ` Konstantin Komarov
2020-09-18 16:54         ` Matthew Wilcox
2020-09-25 16:04           ` Konstantin Komarov
2020-09-18 16:29     ` Konstantin Komarov
2020-09-18 16:38       ` Matthew Wilcox [this message]
2020-09-11 14:10 ` [PATCH v5 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 06/10] fs/ntfs3: Add compression Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2020-09-21 13:26   ` Pali Rohár
2020-09-25 16:30     ` Konstantin Komarov
2020-09-26  8:23       ` Pali Rohár
2020-10-09 15:31         ` Konstantin Komarov
2020-10-09 15:47           ` Pali Rohár
2020-09-11 14:10 ` [PATCH v5 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 10/10] fs/ntfs3: Add MAINTAINERS Konstantin Komarov
     [not found] ` <20200911141018.2457639-3-almaz.alexandrovich@paragon-software.com>
     [not found]   ` <c819ee72-6bb0-416d-dfc4-0bc2ad6d0ccd@harmstone.com>
2020-09-18 16:39     ` [PATCH v5 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
     [not found]   ` <2011cd8c-7dc4-b2e7-114b-d5647336ec92@harmstone.com>
2020-09-18 16:43     ` Konstantin Komarov

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=20200918163814.GF32101@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=aaptel@suse.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=dsterba@suse.cz \
    --cc=joe@perches.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@harmstone.com \
    --cc=nborisov@suse.com \
    --cc=pali@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).