mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] xfs: fixes for 5.18-rc5
Date: Fri, 29 Apr 2022 07:31:57 +1000	[thread overview]
Message-ID: <20220428213157.GT1098723@dread.disaster.area> (raw)
In-Reply-To: <CAHk-=wiVgPPczqyLyOg8fmGYc1z+-ngPKkS_bCTwefcLXfp4CQ@mail.gmail.com>

On Thu, Apr 28, 2022 at 09:46:14AM -0700, Linus Torvalds wrote:
> On Wed, Apr 27, 2022 at 11:19 PM Dave Chinner <david@fromorbit.com> wrote:
> >
> > It's all minor stuff;  a 5.18 build regession fix, a deadlock fix
> > and an update to remove redundant fields from the XFS entry in the
> > MAINTAINERS file.
> 
> Done.

Thanks!

> I had to look twice at that patch going "why does it complain about
> the xfs flags thing" until I realized it was due to XBF_UNMAPPED being
> (1 <<31) and the compiler then seeing explicit negative values being
> assigned.
> 
> We have a lot of "int flags" in various places, very much not just
> xfs, and yeah, we should probably try to clean them up.

Yup, I've already got a bunch of similar cleanup patches for
XFS ready for the next merge window.

> But 99% of the time it's just not worth the noise.

Mostly I agree, but in coverting another dozen+ sets of flags the
biggest benefit I've seen comes from the bit flag definitions all
having a consistent format across the code base.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2022-04-28 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:19 Dave Chinner
2022-04-28 16:46 ` Linus Torvalds
2022-04-28 21:31   ` Dave Chinner [this message]
2022-04-28 18:16 ` pr-tracker-bot

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=20220428213157.GT1098723@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®