Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, Song Liu <song@kernel.org>
Cc: Logan Gunthorpe <logang@deltatee.com>, linux-raid@vger.kernel.org
Subject: Re: [PATCH 2/2] md: return the allocated devices from md_alloc
Date: Mon, 25 Jul 2022 08:27:16 +0200	[thread overview]
Message-ID: <ed9206fa-c047-77bc-918f-ed61fc88631e@suse.de> (raw)
In-Reply-To: <20220723062429.2210193-3-hch@lst.de>

On 7/23/22 08:24, Christoph Hellwig wrote:
> Two callers of md_alloc want to use the newly allocated devices, so
> return it instead of letting them find it cumbersomely after the
> allocation.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>   drivers/md/md-autodetect.c | 22 +++++-----------
>   drivers/md/md.c            | 54 ++++++++++++++++----------------------
>   drivers/md/md.h            |  3 ++-
>   3 files changed, 30 insertions(+), 49 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		           Kernel Storage Architect
hare@suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer

  reply	other threads:[~2022-07-25  6:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23  6:24 md device allocation cleanups Christoph Hellwig
2022-07-23  6:24 ` [PATCH 1/2] md: open code md_probe in autorun_devices Christoph Hellwig
2022-07-25  6:26   ` Hannes Reinecke
2022-07-23  6:24 ` [PATCH 2/2] md: return the allocated devices from md_alloc Christoph Hellwig
2022-07-25  6:27   ` Hannes Reinecke [this message]
2022-07-25 16:30 ` md device allocation cleanups Logan Gunthorpe
2022-07-26  5:15   ` Song Liu

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=ed9206fa-c047-77bc-918f-ed61fc88631e@suse.de \
    --to=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=song@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