From: Mike Snitzer <snitzer@redhat.com>
To: heinzm@redhat.com
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 00/26] dm raid: fix/cleanup for dm-4.8 inclusion
Date: Wed, 13 Jul 2016 10:19:09 -0400 [thread overview]
Message-ID: <20160713141909.GB9378@redhat.com> (raw)
In-Reply-To: <1467825897-26058-1-git-send-email-heinzm@redhat.com>
On Wed, Jul 06 2016 at 1:24pm -0400,
heinzm@redhat.com <heinzm@redhat.com> wrote:
> From: Heinz Mauelshagen <heinzm@redhat.com>
>
>
> Patch series vs. kernel.org linux-dm, branch dm-4.8 to address
> issues identified:
>
> - superfluous memory bariers
> - missing constructor argument checks (sync/nosync)
> - typo in write_mostly constructor argument
> - function argument types
> - recovery ad raid set size issues
> - out-of-place reshape offset checks
> - reject resize during reshape
> - enhance reshape checks
> - avoid memory leaks in destructor
> - comment typos and enhancements
>
> Please review and schedule for 4.8 inclusion
Done, just cleaned up the headers a bit and folded 2 comment specific
patches.
Now staged in linux-next (via linux-dm.git's 'for-next') for 4.8
inclusion.
prev parent reply other threads:[~2016-07-13 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 17:24 [PATCH 00/26] dm raid: fix/cleanup for dm-4.8 inclusion heinzm
2016-07-13 14:19 ` Mike Snitzer [this message]
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=20160713141909.GB9378@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@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).