Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Paul Menzel <pm.debian@googlemail.com>
To: Krzysztof Adamski <k@adamski.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: [md PATCH 1/1] add display of hours remaining to finish resync
Date: Wed, 02 Nov 2011 00:35:10 +0100	[thread overview]
Message-ID: <1320190510.27731.22.camel@mattotaupa> (raw)
In-Reply-To: <1320184427.6471.70.camel@oxygen.netxsys.com>

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

Dear Krzysztof,


Am Dienstag, den 01.11.2011, 17:53 -0400 schrieb Krzysztof Adamski:
> This is my first patch, so please be gentle.

thank you for your patch. The line above does not belong to the commit
message. You can put that below the commit message after »---« or on top
and separate the patch using »--- 8< ----«. (See `git help am` for more
information.

> This patch adds the display of the number of hours till the completion
> of resync of an array in the /proc/mdstat display.
> 
> Example: [>....................]  resync =  3.3% (98633240/2928311808)
> finish=1026.1min (17h) speed=45957K/sec
> 
> Signed-off-by: Krzysztof Adamski <k@adamski.org>
> 
> # diff -Naru drivers/md/md.c-orig  drivers/md/md.c

It would be easier if you used `git commit` and for example

    git format-patch -1 -s

and then sent it using `git send-email` or your MUA (see below).

> --- drivers/md/md.c-orig        2011-10-25 01:11:12.000000000 -0400
> +++ drivers/md/md.c     2011-11-01 17:37:35.000000000 -0400
> @@ -6351,8 +6351,8 @@
>         rt *= dt;
>         rt >>= 5;
>  
> -       seq_printf(seq, " finish=%lu.%lumin", (unsigned long)rt / 60,
> -                  ((unsigned long)rt % 60)/6);
> +       seq_printf(seq, " finish=%lu.%lumin (%luh)", (unsigned long)rt /
> 60,
> +                  ((unsigned long)rt % 60)/6, (unsigned long)rt / 60 /
> 60);

Unfortunately your mailer mangled the patch. You should choose pre
formatted, so automatic line breaks do not happen, which prevent the
application of the patch.

>  
>         seq_printf(seq, " speed=%ldK/sec", db/2/dt);
>  }

Please resend this patch as v2.

    git format-patch --subject-prefix="PATCH v2"

I am not sure if it should be a reply to the same thread or a new
message.

You can add the following line to the the commit message.

Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>

(Different address on purpose.)


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2011-11-01 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 21:53 [md PATCH 1/1] add display of hours remaining to finish resync Krzysztof Adamski
2011-11-01 23:32 ` NeilBrown
2011-11-01 23:35 ` Paul Menzel [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=1320190510.27731.22.camel@mattotaupa \
    --to=pm.debian@googlemail.com \
    --cc=k@adamski.org \
    --cc=linux-raid@vger.kernel.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