public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: torvalds@linux-foundation.org
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: GFS2: Second Pull request (merge window)
Date: Fri, 2 Feb 2018 10:47:30 -0500 (EST)	[thread overview]
Message-ID: <2018618406.6385867.1517586450779.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1118826781.6385862.1517586443478.JavaMail.zimbra@redhat.com>

Hi Linus,

Sorry to bother you with a second merge request for GFS2, but we found
a couple regressions and want to get them fixed in this merge window.

Please consider pulling the following changes for the GFS2 file system.

Regards,

Bob Peterson
----------------------------------------------------------------
The following changes since commit 255442c93843f52b6891b21d0b485bf2c97f93c3:

  Merge tag 'docs-4.16' of git://git.lwn.net/linux (2018-01-31 19:25:25 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-4.16.fixes2

for you to fetch changes up to 7ac07fdaf840f9b141c6d5c286805107227c0e68:

  gfs2: Glock dump performance regression fix (2018-02-01 11:27:11 -0700)

----------------------------------------------------------------
Andreas Gruenbacher wrote two additional patches that we would like
merged in this time. Both are regressions:

1. The first fixes another kernel build dependency problem.
2. The second fixes a performance regression in glock dumps.

----------------------------------------------------------------
Andreas Gruenbacher (2):
      gfs2: Fix the crc32c dependency
      gfs2: Glock dump performance regression fix

 fs/gfs2/Kconfig |  3 +--
 fs/gfs2/glock.c | 65 ++++++++++++++++++++++++++++++++++++++-------------------
 2 files changed, 44 insertions(+), 24 deletions(-)

           reply	other threads:[~2018-02-02 15:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1118826781.6385862.1517586443478.JavaMail.zimbra@redhat.com>]

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=2018618406.6385867.1517586450779.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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