All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] Fix oddity where mdadm did not recognise a relative path
Date: Sun, 29 Jan 2017 18:24:15 +0000	[thread overview]
Message-ID: <588E334F.9070203@youngman.org.uk> (raw)
In-Reply-To: <wrfjzii9iwpq.fsf@gmail.com>

On 29/01/17 17:48, jes.sorensen@gmail.com wrote:
> Wols Lists <antlists@youngman.org.uk> writes:
>> From 4ce784307a9004124392ce48432960d7ca94d0bf Mon Sep 17 00:00:00 2001
>> From: Wol <anthony@youngman.org.uk>
>> Date: Tue, 17 Jan 2017 17:47:05 +0000
>> Subject: [PATCH] Fix oddity where mdadm did not recognise a relative path
>>
>> mdadm assumed that a pathname started with a "/", while an array
>> name didn't. This alters the logic so that if the first character
>> is not a "/" it tries to open an array, and if that fails it drops
>> through to the pathname code rather than terminating immediately
>> with an error.
>>
>> Signed-off-by: Wol <anthony@youngman.org.uk>
>> ---
>>  mdadm.c | 12 ++++++------
>>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> Applied, thanks!
> 
> Sorry I have been swamped the last couple of weeks finishing up my old
> job and starting the new one. Will be bogged down a lot the next couple
> of weeks, so please be patient.
> 
Neil said you were changing jobs - that's fine. I just didn't want it to
get missed, and as there was no initial response I was trying to do as
gentle a "what's up" as I could.

That's fine. If it's in, then great :-) and I can wait for it to be
released whenever.

Cheers,
Wol

  reply	other threads:[~2017-01-29 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 19:07 [PATCH] Fix oddity where mdadm did not recognise a relative path Wols Lists
2017-01-29 17:48 ` jes.sorensen
2017-01-29 18:24   ` Wols Lists [this message]
2017-03-01 22:03 ` jes.sorensen
2017-03-03 18:36   ` Wols Lists

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=588E334F.9070203@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.