From: Andrew Morton <akpm@linux-foundation.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Fabian Frederick <fabf@skynet.be>,
open list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: efs: Fix compilation bug and use pr_debug()
Date: Thu, 4 Jun 2026 19:53:55 -0700 [thread overview]
Message-ID: <20260604195355.c2446336f3f8cdefabadc697@linux-foundation.org> (raw)
In-Reply-To: <CAKqfh0Eu=sp3rfAGzhTPcx1Vw5p=sjxTigAWhkzskYrAWB9iWQ@mail.gmail.com>
On Thu, 4 Jun 2026 20:40:30 -0500 Maxwell Doose <m32285159@gmail.com> wrote:
> On Thu, Jun 4, 2026 at 4:30 PM Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > (cc linux-fsdevel)
> >
>
> Whoops, I guess I'm too reliant on --cc-cmd :(
>
> > On Thu, 4 Jun 2026 15:24:40 -0500 Maxwell Doose <m32285159@gmail.com> wrote:
> >
> > > Firstly, the current code uses formatters that are incompatible with the
> > > most recent GCC for x86_64. Replace them and explicitly cast the
> > > formatted variables to their respective forms of long long.
> >
> > Please quote the compiler output in the changelog.
> >
>
> It's rather lengthy:
> fs/efs/file.c: In function ‘efs_get_block’:
> fs/efs/file.c:26:35: error: ‘block’ undeclared (first use in this
> function); did you mean ‘iblock’?
Right. You're evidently the first person who tried to compile this in
more than 20 years.
How about we just delete it all? If some future developer wants to
know block numbers and stuff, they know how to use printk.
next prev parent reply other threads:[~2026-06-05 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 20:24 Maxwell Doose
2026-06-04 21:30 ` Andrew Morton
2026-06-05 1:40 ` Maxwell Doose
2026-06-05 2:53 ` Andrew Morton [this message]
2026-06-05 3:16 ` Maxwell Doose
2026-06-05 3:27 ` Matthew Wilcox
2026-06-05 3:33 ` Maxwell Doose
2026-06-05 16:59 ` Matthew Wilcox
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=20260604195355.c2446336f3f8cdefabadc697@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@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
all inboxes | Powered by JetHome®