From: Logan Gunthorpe <logang@deltatee.com>
To: Christoph Hellwig <hch@lst.de>, Song Liu <song@kernel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: md device allocation cleanups
Date: Mon, 25 Jul 2022 10:30:28 -0600 [thread overview]
Message-ID: <8663e200-a825-d169-cb27-dff774f0a9ed@deltatee.com> (raw)
In-Reply-To: <20220723062429.2210193-1-hch@lst.de>
On 2022-07-23 00:24, Christoph Hellwig wrote:
> Hi all,
>
> this small series cleans up the mddev allocation a bit by returning
> the structure to callers that want it instead of requiring another
> lookup.
I've reviewed and tested these two patches and they look good to me.
Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
Thanks,
Logan
next prev parent reply other threads:[~2022-07-25 16:30 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
2022-07-25 16:30 ` Logan Gunthorpe [this message]
2022-07-26 5:15 ` md device allocation cleanups 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=8663e200-a825-d169-cb27-dff774f0a9ed@deltatee.com \
--to=logang@deltatee.com \
--cc=hch@lst.de \
--cc=linux-raid@vger.kernel.org \
--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