All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Eryu Guan <eguan@redhat.com>,
	linux-xfs@vger.kernel.org
Subject: Re: minleft fixes V2
Date: Mon, 9 Jan 2017 10:22:06 -0500	[thread overview]
Message-ID: <20170109152205.GA22368@bfoster.bfoster> (raw)
In-Reply-To: <20170108181002.GA3732@birch.djwong.org>

On Sun, Jan 08, 2017 at 10:10:02AM -0800, Darrick J. Wong wrote:
> On Sun, Jan 08, 2017 at 11:10:00AM -0500, Brian Foster wrote:
> > On Sun, Jan 08, 2017 at 11:36:47AM +0100, Christoph Hellwig wrote:
> > > On Wed, Jan 04, 2017 at 06:01:05PM -0800, Darrick J. Wong wrote:
> > > > Ok, sounds good.  I just sent out my first attempt at a pull request to Linus,
> > > > so I'll queue this series for another pull req. after that.
> > > 
> > > I'll resend with a few minor updates based on the comments from Brian
> > > in a few days, so this should be ready for -rc4.
> > 
> > So I just noticed that this series was merged into for-next (which iiuc
> > is easily fixable, yes?).
> 
> Yep.  for-next can be rebased.
> 
> > Christoph already mentioned he was sending a new variant... but
> > juuuuuust a note that not all of these patches had a reviewed-by yet
> > either. ;) 
> 
> <nod> I'm aware; I'll be more patient next time. :)
> 

Thanks. At risk of stating the obvious, I'd much prefer we continue to
follow the "at least one r-b requirement per patch" development model,
even if that means something slips a release (not that this series is at
such a risk). I'm certainly used to that by now... :P

> TBH I was also curious to have the kbuild robot / linux-next pick up a
> changeset that wasn't terribly likely to break anything else, just to
> see how they run...
> 

Hmm, is this something that can be enabled locally (e.g., on posts to
the list) without having to merge stuff prematurely?

Brian

> --D
> 
> > 
> > Brian
> > 
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-01-09 15:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 20:00 minleft fixes V2 Christoph Hellwig
2016-12-22 20:00 ` [PATCH 1/5] xfs: bump up reserved blocks in xfs_alloc_set_aside Christoph Hellwig
2017-01-04 14:33   ` Brian Foster
2017-01-08 10:30     ` Christoph Hellwig
2017-01-08 16:07       ` Brian Foster
2016-12-22 20:00 ` [PATCH 2/5] xfs: fix the alignment fallback in xfs_bmap_btalloc Christoph Hellwig
2017-01-04 14:34   ` Brian Foster
2017-01-08 10:31     ` Christoph Hellwig
2017-01-08 16:08       ` Brian Foster
2016-12-22 20:00 ` [PATCH 3/5] xfs: fix bogus minleft manipulations Christoph Hellwig
2017-01-04 18:19   ` Brian Foster
2017-01-08 10:36     ` Christoph Hellwig
2017-01-08 16:09       ` Brian Foster
2017-01-09 17:56         ` Christoph Hellwig
2016-12-22 20:00 ` [PATCH 4/5] xfs: adjust allocation length in xfs_alloc_space_available Christoph Hellwig
2017-01-04 18:19   ` Brian Foster
2016-12-22 20:00 ` [PATCH 5/5] xfs: don't rely on ->total " Christoph Hellwig
2017-01-04 18:19   ` Brian Foster
2017-01-05  1:21 ` minleft fixes V2 Eryu Guan
2017-01-05  2:01   ` Darrick J. Wong
2017-01-08 10:36     ` Christoph Hellwig
2017-01-08 16:10       ` Brian Foster
2017-01-08 18:10         ` Darrick J. Wong
2017-01-09 15:22           ` Brian Foster [this message]
2017-01-09 15:34             ` Christoph Hellwig
2017-01-09 15:43               ` Brian Foster
2017-01-10  4:23             ` Darrick J. Wong

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=20170109152205.GA22368@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=eguan@redhat.com \
    --cc=hch@lst.de \
    --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.