public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: WenRuo Qu <wqu@suse.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/5] btrfs: prepare for larger folios support
Date: Fri, 21 Feb 2025 11:23:00 +0000	[thread overview]
Message-ID: <c9e1a407-6562-4564-a87a-e449d36b4b97@wdc.com> (raw)
In-Reply-To: <cover.1740043233.git.wqu@suse.com>

On 20.02.25 10:26, Qu Wenruo wrote:
> Qu Wenruo (5):
>    btrfs: prepare subpage.c for larger folios support
>    btrfs: remove the PAGE_SIZE usage inside inline extent reads
>    btrfs: prepare btrfs_launcher_folio() for larger folios support
>    btrfs: prepare extent_io.c for future larger folio support
>    btrfs: prepare btrfs_page_mkwrite() for larger folios
> 
>   fs/btrfs/extent_io.c | 50 +++++++++++++++++++++++++-------------------
>   fs/btrfs/file.c      | 19 +++++++++--------
>   fs/btrfs/inode.c     |  8 +++----
>   fs/btrfs/subpage.c   | 36 +++++++++++++++----------------
>   fs/btrfs/subpage.h   | 24 ++++++++-------------
>   5 files changed, 69 insertions(+), 68 deletions(-)
> 

Hi Qu,
What am I doing wrong?

Applying: btrfs: prepare subpage.c for larger folios support
Applying: btrfs: remove the PAGE_SIZE usage inside inline extent reads
In file included from ./include/linux/kernel.h:28,
                  from ./include/linux/cpumask.h:11,
                  from ./include/linux/smp.h:13,
                  from ./include/linux/lockdep.h:14,
                  from ./include/linux/spinlock.h:63,
                  from ./include/linux/swait.h:7,
                  from ./include/linux/completion.h:12,
                  from ./include/linux/crypto.h:15,
                  from ./include/crypto/hash.h:12,
                  from fs/btrfs/inode.c:6:
fs/btrfs/inode.c: In function ‘uncompress_inline’:
fs/btrfs/inode.c:6807:41: error: ‘sectorsize’ undeclared (first use in 
this function); did you mean ‘sector_t’?
  6807 |         max_size = min_t(unsigned long, sectorsize, max_size);
       |                                         ^~~~~~~~~~
./include/linux/minmax.h:86:23: note: in definition of macro 
‘__cmp_once_unique’
    86 |         ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
       |                       ^
./include/linux/minmax.h:161:27: note: in expansion of macro ‘__cmp_once’
   161 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
       |                           ^~~~~~~~~~
fs/btrfs/inode.c:6807:20: note: in expansion of macro ‘min_t’
  6807 |         max_size = min_t(unsigned long, sectorsize, max_size);
       |                    ^~~~~
fs/btrfs/inode.c:6807:41: note: each undeclared identifier is reported 
only once for each function it appears in
  6807 |         max_size = min_t(unsigned long, sectorsize, max_size);
       |                                         ^~~~~~~~~~
./include/linux/minmax.h:86:23: note: in definition of macro 
‘__cmp_once_unique’
    86 |         ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
       |                       ^
./include/linux/minmax.h:161:27: note: in expansion of macro ‘__cmp_once’
   161 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
       |                           ^~~~~~~~~~
fs/btrfs/inode.c:6807:20: note: in expansion of macro ‘min_t’
  6807 |         max_size = min_t(unsigned long, sectorsize, max_size);
       |                    ^~~~~
fs/btrfs/inode.c: In function ‘read_inline_extent’:
fs/btrfs/inode.c:6841:32: error: ‘sectorsize’ undeclared (first use in 
this function); did you mean ‘sector_t’?
  6841 |         copy_size = min_t(u64, sectorsize,
       |                                ^~~~~~~~~~
./include/linux/minmax.h:86:23: note: in definition of macro 
‘__cmp_once_unique’
    86 |         ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
       |                       ^
./include/linux/minmax.h:161:27: note: in expansion of macro ‘__cmp_once’
   161 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
       |                           ^~~~~~~~~~
fs/btrfs/inode.c:6841:21: note: in expansion of macro ‘min_t’
  6841 |         copy_size = min_t(u64, sectorsize,
       |                     ^~~~~
make[4]: *** [scripts/Makefile.build:207: fs/btrfs/inode.o] Error 1
make[3]: *** [scripts/Makefile.build:465: fs/btrfs] Error 2
make[2]: *** [scripts/Makefile.build:465: fs] Error 2
make[1]: *** [/home/johannes/src/linux/Makefile:1989: .] Error 2

  parent reply	other threads:[~2025-02-21 11:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  9:22 [PATCH 0/5] btrfs: prepare for larger folios support Qu Wenruo
2025-02-20  9:22 ` [PATCH 1/5] btrfs: prepare subpage.c " Qu Wenruo
2025-02-21 12:06   ` Johannes Thumshirn
2025-02-22  5:03     ` Qu Wenruo
2025-02-20  9:22 ` [PATCH 2/5] btrfs: remove the PAGE_SIZE usage inside inline extent reads Qu Wenruo
2025-02-21 11:37   ` Johannes Thumshirn
2025-02-20  9:22 ` [PATCH 3/5] btrfs: prepare btrfs_launcher_folio() for larger folios support Qu Wenruo
2025-02-21 12:08   ` Johannes Thumshirn
2025-02-20  9:22 ` [PATCH 4/5] btrfs: prepare extent_io.c for future larger folio support Qu Wenruo
2025-02-21 12:12   ` Johannes Thumshirn
2025-02-22  5:02     ` Qu Wenruo
2025-02-25 18:41   ` Nathan Chancellor
2025-02-20  9:22 ` [PATCH 5/5] btrfs: prepare btrfs_page_mkwrite() for larger folios Qu Wenruo
2025-02-21 12:22   ` Johannes Thumshirn
2025-02-21 11:23 ` Johannes Thumshirn [this message]
2025-02-21 12:34   ` [PATCH 0/5] btrfs: prepare for larger folios support Filipe Manana
2025-02-21 22:33   ` Qu Wenruo

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=c9e1a407-6562-4564-a87a-e449d36b4b97@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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