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] [PATCH 00/17] DLM: dlm patches need review
Date: Wed, 9 Aug 2017 12:35:54 +0100	[thread overview]
Message-ID: <34d7ef0e-235a-1348-a423-780fb222ab05@redhat.com> (raw)
In-Reply-To: <37e08b5b0047440cb1edcd5904139b04@TGXML394.toshiba.local>

Hi,


On 09/08/17 06:36, tsutomu.owa at toshiba.co.jp wrote:
> Hi,
>
> This series of patches is to fix various bugs.  This patch set is against the mainline kernel.
> I'd like reviewed to make sure those changes are fine.
>
> Patch number 01/02/03 were posted on this mailing list by Bob Peterson <rpeterso@redhat.com>.
> Patch 03 is modified to correct a bug acquiring rwlock multiple times.
> Other than that, there is no changes.
>
> 01:
> https://www.redhat.com/archives/cluster-devel/2017-April/msg00021.html
> 02:
> https://www.redhat.com/archives/cluster-devel/2017-April/msg00022.html
> 03:
> https://www.redhat.com/archives/cluster-devel/2017-April/msg00023.html
>
> thanks in advance.
> -- owa
> ps. Sorry to bother you if you got those mails several times.
>
>

Many thanks for looking so closely at the DLM and in sending this patch  
set. Some of the patches I can see are obvious fixes and others I'd need  
a bit more time to look at to be sure about. I've sent a few individual  
comments for some of the patches. However overall this looks like a  
really good set of patches, and I'm sure took some time for you to put  
together. I think the best thing would be for us to get these patches  
into a kernel now and run some tests, since there is quite a lot of change,

Steve.




  reply	other threads:[~2017-08-09 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  5:36 [Cluster-devel] [PATCH 00/17] DLM: dlm patches need review tsutomu.owa
2017-08-09 11:35 ` Steven Whitehouse [this message]
2017-08-10  5:50   ` tsutomu.owa

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=34d7ef0e-235a-1348-a423-780fb222ab05@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).