From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@suse.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
David Sterba <dsterba@suse.com>, Qu Wenruo <wqu@suse.com>
Subject: Re: [linux-next:pending-fixes 207/319] fs/btrfs/qgroup.c:2014:6: error: use of undeclared identifier 'bytenr'
Date: Wed, 9 Oct 2024 13:30:30 +0200 [thread overview]
Message-ID: <20241009113029.GJ1609@suse.cz> (raw)
In-Reply-To: <CAKisOQHVBRbpsDnWRa40Rga1hjW_5xuwPAshXY=6+nNb6O8OOg@mail.gmail.com>
On Wed, Oct 09, 2024 at 11:09:13AM +0100, Filipe Manana wrote:
> On Wed, Oct 9, 2024 at 3:55 AM kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
> > head: 47fa0de9b07c6214b57458e965646a3e25656b69
> > commit: 5c0ea18d992fffc948e087c0002560d747e6edd9 [207/319] btrfs: use sector numbers as keys for the dirty extents xarray
> > config: arm-randconfig-002-20241009 (https://download.01.org/0day-ci/archive/20241009/202410091038.SI34ZULQ-lkp@intel.com/config)
> > compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241009/202410091038.SI34ZULQ-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202410091038.SI34ZULQ-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > >> fs/btrfs/qgroup.c:2014:6: error: use of undeclared identifier 'bytenr'
> > if (bytenr >= MAX_LFS_FILESIZE) {
>
> Ah this should be record->bytenr.
> The issue is actually fixed in a later patch of the same patchset,
> where bytenr is a function argument.
>
> I can update the patch but then it will require updating the patches
> that come next from the same patchset and rebasing the for-next
> branch.
> And I see it's already in the next-fixes branch.
>
> David, how do you prefer to proceed here? Do you want me to fix this
> and resend the patchset?
No need to resend, I'll fix it locally, the patch in next-fixes was the
old one so I'll sync it with what's in our development for-next (and
also check the others just in case). I'll also check and update all the
branches involved in the for-next pulled by linux-next.
next prev parent reply other threads:[~2024-10-09 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 2:54 kernel test robot
2024-10-09 10:09 ` Filipe Manana
2024-10-09 11:30 ` David Sterba [this message]
2024-10-14 16:26 ` Filipe Manana
2024-10-14 22:06 ` David Sterba
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=20241009113029.GJ1609@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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