cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 Pre-pull patch posting (merge window)
Date: Thu,  5 Sep 2013 10:02:06 +0100	[thread overview]
Message-ID: <1378371732-3947-1-git-send-email-swhiteho@redhat.com> (raw)

Hi,

This is the smallest merge window patch set for GFS2 for quite
some time. Only one of the patches (moving gfs2_sync_meta) is
a non-bug fix patch, although the merge ordered and writeback
writepage patch is also a nice clean up.

A couple of the patches are quite recently added, due to my only
having recently returned from holiday, so I'll give them a couple
of extra days in -next before sending the pull request.

Steve.



             reply	other threads:[~2013-09-05  9:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05  9:02 Steven Whitehouse [this message]
2013-09-05  9:02 ` [Cluster-devel] [PATCH 1/6] GFS2: Move gfs2_sync_meta to lops.c Steven Whitehouse
2013-09-05  9:02 ` [Cluster-devel] [PATCH 2/6] GFS2: Take glock reference in examine_bucket() Steven Whitehouse
2013-09-05  9:02 ` [Cluster-devel] [PATCH 3/6] GFS2: Merge ordered and writeback writepage Steven Whitehouse
2013-09-05  9:02 ` [Cluster-devel] [PATCH 4/6] GFS2: Remove unnecessary memory barrier Steven Whitehouse
2013-09-05  9:02 ` [Cluster-devel] [PATCH 5/6] GFS2: Don't flag consistency error if first mounter is a spectator Steven Whitehouse
2013-09-05  9:02 ` [Cluster-devel] [PATCH 6/6] GFS2: dirty inode correctly in gfs2_write_end Steven Whitehouse
  -- strict thread matches above, loose matches on Subject: below --
2014-12-08 12:38 [Cluster-devel] GFS2: Pre-pull patch posting (merge window) Steven Whitehouse
2014-10-08  9:53 Steven Whitehouse
2014-06-03 11:02 Steven Whitehouse
2014-04-01  9:15 Steven Whitehouse
2014-01-20 12:23 Steven Whitehouse
2013-11-04 11:09 Steven Whitehouse
2013-07-01  9:33 Steven Whitehouse
2013-04-26  9:18 Steven Whitehouse
2013-02-19 10:07 Steven Whitehouse
2012-11-30  9:52 Steven Whitehouse
2012-09-26  8:25 Steven Whitehouse
2012-07-23  8:00 Steven Whitehouse
2012-05-17 12:23 Steven Whitehouse
2012-03-19 10:25 Steven Whitehouse
     [not found] ` <4F674696.7030602@xenotime.net>
2012-03-19 14:59   ` Steven Whitehouse
     [not found]     ` <4F674E4F.5080904@xenotime.net>
2012-03-19 15:34       ` Steven Whitehouse
2012-03-23 19:41         ` David Teigland
2012-03-23 19:46           ` David Miller
     [not found]           ` <4F6CD7AD.9030306@xenotime.net>
2012-03-23 20:09             ` Steven Whitehouse
2012-03-23 20:18             ` David Teigland
     [not found]               ` <20120323220618.GA30906@d2.synalogic.ca>
2012-03-26 10:44                 ` Steven Whitehouse
     [not found]                   ` <4F79C733.60604@xenotime.net>
2012-04-02 15:47                     ` Steven Whitehouse
2012-03-20  9:47       ` Steven Whitehouse
2012-01-05 11:51 Steven Whitehouse
2011-10-24 12:48 Steven Whitehouse
2011-07-22  9:16 Steven Whitehouse
2011-05-19  8:46 Steven Whitehouse
2011-03-15  9:11 Steven Whitehouse

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=1378371732-3947-1-git-send-email-swhiteho@redhat.com \
    --to=swhiteho@redhat.com \
    /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).