linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux RAID <linux-raid@vger.kernel.org>,
	Sebastian Riemer <sebastian.riemer@profitbricks.com>,
	Jim Kukunas <james.t.kukunas@linux.intel.com>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: [PULL REQUEST] md fixes for 3.5-rc
Date: Wed, 6 Jun 2012 09:01:13 +1000	[thread overview]
Message-ID: <20120606090113.07c78064@notabene.brown> (raw)

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]


Hi Linus,
 a couple of little md fixes for 3.5.
Thanks,
NeilBrown


The following changes since commit 1e2aec873ad6d16538512dbb96853caa1fa076af:

  Merge branch 'generic-string-functions' (2012-05-26 16:57:16 -0700)

are available in the git repository at:


  git://neil.brown.name/md/ tags/md-3.5-fixes

for you to fetch changes up to aba336bd1d46d6b0404b06f6915ed76150739057:

  md: raid1/raid10: fix problem with merge_bvec_fn (2012-05-31 15:56:30 +1000)

----------------------------------------------------------------
md: 2 fixes for 3.5-rc

One sparse-warning fix, one bigfix for 3.4-stable

----------------------------------------------------------------
Jim Kukunas (1):
      lib/raid6: fix sparse warnings in recovery functions

NeilBrown (1):
      md: raid1/raid10: fix problem with merge_bvec_fn

 drivers/md/raid1.c      |    4 ++++
 drivers/md/raid10.c     |    4 ++++
 lib/raid6/recov.c       |    7 ++++---
 lib/raid6/recov_ssse3.c |    7 ++++---
 4 files changed, 16 insertions(+), 6 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

             reply	other threads:[~2012-06-05 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 23:01 NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-03  7:53 [PULL REQUEST] md fixes for 3.5-rc NeilBrown

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=20120606090113.07c78064@notabene.brown \
    --to=neilb@suse.de \
    --cc=fengguang.wu@intel.com \
    --cc=james.t.kukunas@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sebastian.riemer@profitbricks.com \
    --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;
as well as URLs for NNTP newsgroup(s).