All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Pull request
Date: Tue, 24 Jun 2008 22:12:47 +0100	[thread overview]
Message-ID: <1214341967.4266.28.camel@localhost.localdomain> (raw)

Hi,

Please consider pulling the following GFS2 bug fixes,

Steve.

-------------------------------------------------------------------------------------
The following changes since commit 62786b9e81a2dbe9c073a2ade52d33a2627d6d85:
  Linus Torvalds (1):
        Merge branch 'hotfixes' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6

are found in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-fixes.git

Benjamin Marzinski (1):
      [GFS2] fix gfs2 block allocation (cleaned up)

Bob Peterson (1):
      [GFS2] BUG: unable to handle kernel paging request at ffff81002690e000

 fs/gfs2/bmap.c |   23 +++++++++--------------
 fs/gfs2/rgrp.c |    2 +-
 2 files changed, 10 insertions(+), 15 deletions(-)




WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: torvalds@linux-foundation.org
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GFS2] Pull request
Date: Tue, 24 Jun 2008 22:12:47 +0100	[thread overview]
Message-ID: <1214341967.4266.28.camel@localhost.localdomain> (raw)

Hi,

Please consider pulling the following GFS2 bug fixes,

Steve.

-------------------------------------------------------------------------------------
The following changes since commit 62786b9e81a2dbe9c073a2ade52d33a2627d6d85:
  Linus Torvalds (1):
        Merge branch 'hotfixes' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6

are found in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-fixes.git

Benjamin Marzinski (1):
      [GFS2] fix gfs2 block allocation (cleaned up)

Bob Peterson (1):
      [GFS2] BUG: unable to handle kernel paging request at ffff81002690e000

 fs/gfs2/bmap.c |   23 +++++++++--------------
 fs/gfs2/rgrp.c |    2 +-
 2 files changed, 10 insertions(+), 15 deletions(-)



             reply	other threads:[~2008-06-24 21:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 21:12 Steven Whitehouse [this message]
2008-06-24 21:12 ` [GFS2] Pull request Steven Whitehouse
  -- strict thread matches above, loose matches on Subject: below --
2019-05-08 11:48 [Cluster-devel] GFS2: Pull Request Andreas Gruenbacher
2019-05-08 17:55 ` Linus Torvalds
2019-05-08 18:06   ` Linus Torvalds
2019-05-08 20:17     ` Andreas Gruenbacher
2019-05-08 20:21       ` Linus Torvalds
2019-05-08 20:58       ` Jonathan Corbet
2019-05-08 21:05         ` Linus Torvalds
2019-05-08 21:50           ` Jonathan Corbet
2010-05-18  8:38 [Cluster-devel] GFS2: Pull request Steven Whitehouse
2010-03-02 11:03 Steven Whitehouse
2009-12-03 15:01 Steven Whitehouse
2009-09-14  8:08 Steven Whitehouse
2009-06-11 10:51 Steven Whitehouse
2009-04-15 11:26 Steven Whitehouse
2009-03-24 12:20 Steven Whitehouse
2009-01-05  9:34 Steven Whitehouse
2008-10-10  8:05 [Cluster-devel] [GFS2] " Steven Whitehouse
2008-07-14 16:03 Steven Whitehouse
2008-05-20  9:12 [Cluster-devel] [GFS2] Pre-pull patch posting (bug fixes) swhiteho
2008-05-20 10:05 ` [Cluster-devel] [GFS2] Pull request Steven Whitehouse
2008-04-18 16:53 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=1214341967.4266.28.camel@localhost.localdomain \
    --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 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.