public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 0/2] common: make common/rc easier to manage
Date: Thu, 1 Dec 2016 12:18:15 +0800	[thread overview]
Message-ID: <20161201041815.GB29149@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20161130211104.GB11750@dastard>

On Thu, Dec 01, 2016 at 08:11:04AM +1100, Dave Chinner wrote:
> On Wed, Nov 30, 2016 at 06:10:28PM +0800, Eryu Guan wrote:
> > On Wed, Nov 30, 2016 at 08:32:31AM +1100, Dave Chinner wrote:
> > > Hi folks,
> > > 
> > > common/rc has grown huge with lots of library functions, and it's
> > > becoming hard to manage. The following two patches split the XFS and
> > > btrfs specific functionality in common/rc into separate files which
> > > are sourced directly from common/rc based on $FSTYP.
> > 
> > Thanks, Dave!
> > 
> > > 
> > > This moves a large chunk of code spread throughout common/rc into
> > > smaller, more contained files where it is easier to see how the
> > > filesystem specific pieces are put together. I'd like to see this
> > > happen for other filesytems, and quite possibly other groups of
> > > functionality that make sense to manage separately.
> > > 
> > > Thoughts and comments welcome!
> > 
> > They look good to me, and I'm testing them now. Two things I noticed:
> > - Can we take this opportunity to fix some code style issues, along with
> >   the movement? e.g. tab indention, if-then-else-fi format and while-do
> >   format and whitespace issues.
> 
> In the patch that moves the code, no. In follow-on cleanup patches,
> yes.

I'll post a cleanup patch soon.

> 
> > - Should _require_scratch_richacl_xfs() be moved to common/xfs too?
> 
> I ignored that for the moment because XFS doesn't actually have any
> richacl support and I didn't want to think about how the richacl
> checks might be best separated.

OK, let's keep it in common/rc for now.

Thanks,
Eryu

      reply	other threads:[~2016-12-01  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 21:32 [PATCH 0/2] common: make common/rc easier to manage Dave Chinner
2016-11-29 21:32 ` [PATCH 1/2] common: split XFS functions from common/rc Dave Chinner
2016-11-29 23:24   ` Darrick J. Wong
2016-11-29 21:32 ` [PATCH 2/2] common: split Btrfs " Dave Chinner
2016-11-30 10:10 ` [PATCH 0/2] common: make common/rc easier to manage Eryu Guan
2016-11-30 21:11   ` Dave Chinner
2016-12-01  4:18     ` Eryu Guan [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=20161201041815.GB29149@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=david@fromorbit.com \
    --cc=fstests@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