From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/15] xfsprogs: sparse fixes
Date: Fri, 5 Oct 2018 08:41:23 -0700 [thread overview]
Message-ID: <20181005154123.GQ19324@magnolia> (raw)
In-Reply-To: <1538712196-13625-1-git-send-email-sandeen@sandeen.net>
On Thu, Oct 04, 2018 at 11:03:01PM -0500, Eric Sandeen wrote:
> A handful of sparse fixes, more or less one patch per issue.
Mostly looks fine except for the things I complained about on IRC:
Patch 7 commit message ought to identify the other definer of MS_
constants.
Patch 14 commit message has a typo "activel".
*progname probably should be in libfrog.h so that scrub doesn't
have to include libxfs.h (scrub doesn't link against libxfs) (patch 11).
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
>
> -Eric
>
next prev parent reply other threads:[~2018-10-05 22:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 4:03 [PATCH 0/15] xfsprogs: sparse fixes Eric Sandeen
2018-10-05 4:03 ` [PATCH 01/15] xfsprogs: minor " Eric Sandeen
2018-10-06 10:07 ` Christoph Hellwig
2018-10-08 14:58 ` Eric Sandeen
2018-10-05 4:03 ` [PATCH 02/15] xfsprogs: use ANSI declarations of void-arg functions Eric Sandeen
2018-10-06 10:07 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 03/15] mkfs.xfs: include full parser prototype in subopts definition Eric Sandeen
2018-10-06 10:08 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 04/15] xfs_db: single-bit bitfields are unsigned Eric Sandeen
2018-10-06 10:08 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 05/15] xfsprogs: don't use 0 as pointer Eric Sandeen
2018-10-06 10:08 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 06/15] xfsprogs: minor endian annotation fixes Eric Sandeen
2018-10-06 10:11 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 07/15] libxfs: avoid redefinitions of macros in mount.h Eric Sandeen
2018-10-06 10:12 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 08/15] xfsprogs: avoid redefinition of NBBY Eric Sandeen
2018-10-06 10:12 ` Christoph Hellwig
2018-10-08 14:59 ` Eric Sandeen
2018-10-05 4:03 ` [PATCH 09/15] xfsprogs: remove write-only variables Eric Sandeen
2018-10-06 10:13 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 10/15] xfsprogs: make static things static Eric Sandeen
2018-10-06 10:13 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 11/15] xfsprogs: include headers for extern variables Eric Sandeen
2018-10-06 10:14 ` Christoph Hellwig
2018-10-08 17:08 ` Eric Sandeen
2018-10-05 4:03 ` [PATCH 12/15] xfsprogs: kill EXTERN macro Eric Sandeen
2018-10-06 10:15 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 13/15] libxfs: export unused nonstatic functions to quiet static checkers Eric Sandeen
2018-10-06 10:15 ` Christoph Hellwig
2018-10-05 4:03 ` [PATCH 14/15] xfsprogs: eliminate shadow variables Eric Sandeen
2018-10-06 10:16 ` Christoph Hellwig
2018-10-08 15:48 ` Eric Sandeen
2018-10-05 4:03 ` [PATCH 15/15] libfrog: change project entity variable scope Eric Sandeen
2018-10-06 10:18 ` Christoph Hellwig
2018-10-08 15:50 ` Eric Sandeen
2018-10-05 15:41 ` Darrick J. Wong [this message]
2018-10-05 15:52 ` [PATCH 0/15] xfsprogs: sparse fixes Eric Sandeen
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=20181005154123.GQ19324@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).