stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rainer Fiebig <jrf@mailbox.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Sasha Levin <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors"
Date: Sat, 2 Mar 2024 18:03:31 +0100	[thread overview]
Message-ID: <2024030214-scratch-compactly-638f@gregkh> (raw)
In-Reply-To: <b0f08ff8-bddf-309d-4c30-1246e80f3f44@mailbox.org>

On Sat, Mar 02, 2024 at 10:30:54AM +0100, Rainer Fiebig wrote:
> Am 01.03.24 um 18:56 schrieb Nathan Chancellor:
> > On Fri, Mar 01, 2024 at 03:42:17PM +0100, Rainer Fiebig wrote:
> >> fs/ntfs3/frecord.c: In Funktion »ni_read_frame«:
> >> fs/ntfs3/frecord.c:2460:16: Error: variable >>i_size<< is not used"
> >> [-Werror=unused-variable]
> >>  2460 |         loff_t i_size = i_size_read(&ni->vfs_inode);
> >>       |                ^~~~~~
> > 
> > This is a regression that was inherited from mainline because
> > commit 4fd6c08a16d7 ("fs/ntfs3: Use i_size_read and i_size_write") was
> > applied to stable without commit c8e314624a16 ("fs/ntfs3: fix build
> > without CONFIG_NTFS3_LZX_XPRESS").
> With  CONFIG_NTFS3_LZX_XPRESS=y  the build was fine.

Thanks for the report, will go do a new release with this fix in it.

greg k-h

      reply	other threads:[~2024-03-02 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 14:42 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors" Rainer Fiebig
2024-03-01 17:56 ` Nathan Chancellor
2024-03-02  9:30   ` Rainer Fiebig
2024-03-02 17:03     ` Greg Kroah-Hartman [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=2024030214-scratch-compactly-638f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jrf@mailbox.org \
    --cc=nathan@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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).