linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Create.c: close mdfd and generate uevent
Date: Wed, 25 Nov 2020 18:06:35 -0500	[thread overview]
Message-ID: <4a43d8a1-be94-2fdc-a9b2-08906be167e5@trained-monkey.org> (raw)
In-Reply-To: <20201124123949.792-1-mariusz.tkaczyk@linux.intel.com>

On 11/24/20 7:39 AM, Mariusz Tkaczyk wrote:
> During mdfd closing change event is not generated because open() is
> called before start watching mddevice by udev.
> Device is ready at this stage. Unblock device, close fd and
> generate event to give a chance next layers to work.
> 
> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
> ---
>  Create.c | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)

Applied!

Thanks,
Jes


      reply	other threads:[~2020-11-25 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 12:39 [PATCH] Create.c: close mdfd and generate uevent Mariusz Tkaczyk
2020-11-25 23:06 ` Jes Sorensen [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=4a43d8a1-be94-2fdc-a9b2-08906be167e5@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mariusz.tkaczyk@linux.intel.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).