From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 08/12] libfrog: move workqueue.h to libfrog/
Date: Thu, 5 Sep 2019 09:34:47 +1000 [thread overview]
Message-ID: <20190904233447.GW1119@dread.disaster.area> (raw)
In-Reply-To: <156757179417.1838135.16722106490569097057.stgit@magnolia>
On Tue, Sep 03, 2019 at 09:36:34PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Move this header to libfrog since the code is there already.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> include/workqueue.h | 41 -----------------------------------------
> libfrog/Makefile | 3 ++-
> libfrog/workqueue.h | 41 +++++++++++++++++++++++++++++++++++++++++
> repair/threads.h | 2 +-
> scrub/fscounters.c | 2 +-
> scrub/inodes.c | 2 +-
> scrub/phase1.c | 2 +-
> scrub/phase2.c | 2 +-
> scrub/phase3.c | 2 +-
> scrub/phase4.c | 2 +-
> scrub/phase5.c | 2 +-
> scrub/phase6.c | 2 +-
> scrub/read_verify.c | 2 +-
> scrub/spacemap.c | 2 +-
> scrub/vfs.c | 2 +-
> 15 files changed, 55 insertions(+), 54 deletions(-)
> delete mode 100644 include/workqueue.h
> create mode 100644 libfrog/workqueue.h
ok.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
> diff --git a/libfrog/workqueue.h b/libfrog/workqueue.h
> new file mode 100644
> index 00000000..a1f3a57c
> --- /dev/null
> +++ b/libfrog/workqueue.h
> @@ -0,0 +1,41 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * Copyright (C) 2017 Oracle. All Rights Reserved.
> + * Author: Darrick J. Wong <darrick.wong@oracle.com>
> + */
> +#ifndef __LIBFROG_WORKQUEUE_H__
> +#define __LIBFROG_WORKQUEUE_H__
FWIW, I like that these all have consistent guards now :)
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-09-04 23:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 4:35 [PATCH 00/12] libfrog: move header files Darrick J. Wong
2019-09-04 4:35 ` [PATCH 01/12] libxfs: move topology declarations into separate header Darrick J. Wong
2019-09-04 23:24 ` Dave Chinner
2019-09-04 4:35 ` [PATCH 02/12] libfrog: move avl64.h to libfrog/ Darrick J. Wong
2019-09-04 23:25 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 03/12] libfrog: move bitmap.h " Darrick J. Wong
2019-09-04 23:28 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 04/12] libfrog: move convert.h " Darrick J. Wong
2019-09-04 23:28 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 05/12] libfrog: move fsgeom.h " Darrick J. Wong
2019-09-04 23:32 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 06/12] libfrog: move ptvar.h " Darrick J. Wong
2019-09-04 23:32 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 07/12] libfrog: move radix-tree.h " Darrick J. Wong
2019-09-04 23:33 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 08/12] libfrog: move workqueue.h " Darrick J. Wong
2019-09-04 23:34 ` Dave Chinner [this message]
2019-09-04 4:36 ` [PATCH 09/12] libfrog: move crc32c.h " Darrick J. Wong
2019-09-04 23:37 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 10/12] libfrog: move path.h " Darrick J. Wong
2019-09-04 23:39 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 11/12] libfrog: move workqueue.h " Darrick J. Wong
2019-09-04 23:40 ` Dave Chinner
2019-09-04 4:36 ` [PATCH 12/12] libfrog: move libfrog.h to libfrog/util.h Darrick J. Wong
2019-09-04 23:43 ` Dave Chinner
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=20190904233447.GW1119@dread.disaster.area \
--to=david@fromorbit.com \
--cc=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).