public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Carlos Maiolino <cem@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH V2] xfs: Comment out unreachable code within xchk_fscounters()
Date: Wed, 7 Jun 2023 07:53:50 -0700	[thread overview]
Message-ID: <20230607145350.GS1325469@frogsfrogsfrogs> (raw)
In-Reply-To: <ZICUn0Na/mqWEKkw@infradead.org>

On Wed, Jun 07, 2023 at 07:30:55AM -0700, Christoph Hellwig wrote:
> On Wed, Jun 07, 2023 at 07:28:12AM -0700, Darrick J. Wong wrote:
> > *Someone* please just review the fixes for fscounters.c that I put on
> > the list two weeks ago.  The first two patches of the patchset are
> > sufficient to fix this problem.
> > 
> > https://lore.kernel.org/linux-xfs/168506061483.3732954.5178462816967376906.stgit@frogsfrogsfrogs/
> 
> That sounds like a way better idea indeed.  I'll get to it after my
> meetings.

FYI there's a parallel discussion about the same patch going on fsdevel:

https://lore.kernel.org/linux-fsdevel/20230522234200.GC11598@frogsfrogsfrogs/

--D

      reply	other threads:[~2023-06-07 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 15:11 [PATCH V2] xfs: Comment out unreachable code within xchk_fscounters() cem
2023-06-06 15:17 ` Darrick J. Wong
2023-06-07  6:39 ` Christoph Hellwig
2023-06-07  7:37   ` Carlos Maiolino
2023-06-07  7:48     ` Christoph Hellwig
2023-06-07  8:48       ` Carlos Maiolino
2023-06-07 14:28         ` Darrick J. Wong
2023-06-07 14:30           ` Christoph Hellwig
2023-06-07 14:53             ` Darrick J. Wong [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=20230607145350.GS1325469@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@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