From: Christoph Hellwig <hch@lst.de>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: generic/232 regression - bda250db ("xfs: rewrite xfs_dq_get_next_id using xfs_iext_lookup_extent")
Date: Wed, 5 Jul 2017 17:22:59 +0200 [thread overview]
Message-ID: <20170705152259.GA2593@lst.de> (raw)
In-Reply-To: <20170705151158.GC51285@bfoster.bfoster>
Thanks Brian,
your fix looks correct to me. I usually got for curly braces on
both sides of the else if they are needed, but thay might be a bit
too nitpicky..
next parent reply other threads:[~2017-07-05 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170705151158.GC51285@bfoster.bfoster>
2017-07-05 15:22 ` Christoph Hellwig [this message]
2017-07-05 15:27 ` generic/232 regression - bda250db ("xfs: rewrite xfs_dq_get_next_id using xfs_iext_lookup_extent") Brian Foster
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=20170705152259.GA2593@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.