From: Christoph Hellwig <hch@infradead.org>
To: Mauricio Faria de Oliveira <mfo@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"Isaac J. Manjarres" <isaacmanjarres@google.com>
Subject: Re: [PATCH RESEND 1/2] loop: deprecate autoloading callback loop_probe()
Date: Thu, 20 Jul 2023 01:30:36 -0700 [thread overview]
Message-ID: <ZLjwrNntqIEb7QQe@infradead.org> (raw)
In-Reply-To: <20230717191628.582363-2-mfo@canonical.com>
On Mon, Jul 17, 2023 at 04:16:27PM -0300, Mauricio Faria de Oliveira wrote:
> The 'probe' callback in __register_blkdev() is only used
> under the CONFIG_BLOCK_LEGACY_AUTOLOAD deprecation guard.
>
> The loop_probe() function is only used for that callback,
> so guard it too, accordingly.
>
> See commit fbdee71bb5d8 ("block: deprecate autoloading based on dev_t").
>
> Signed-off-by: Mauricio Faria de Oliveira <mfo@canonical.com>
> ---
> drivers/block/loop.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index 37511d2b2caf..7268ff71c92c 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -2093,6 +2093,7 @@ static void loop_remove(struct loop_device *lo)
> put_disk(lo->lo_disk);
> }
>
> +#ifdef CONFIG_BLOCK_LEGACY_AUTOLOAD
> static void loop_probe(dev_t dev)
> {
> int idx = MINOR(dev) >> part_shift;
> @@ -2101,6 +2102,7 @@ static void loop_probe(dev_t dev)
> return;
> loop_add(idx);
> }
> +#endif
Turn this into..
#else
#define loop_probe NULL
#endif /* !CONFIG_BLOCK_LEGACY_AUTOLOAD */
and you can skip the pretty ugly second hunk.
next prev parent reply other threads:[~2023-07-20 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 19:16 [PATCH RESEND 0/2] loop: fix regression from max_loop default value change Mauricio Faria de Oliveira
2023-07-17 19:16 ` [PATCH RESEND 1/2] loop: deprecate autoloading callback loop_probe() Mauricio Faria de Oliveira
2023-07-20 8:30 ` Christoph Hellwig [this message]
2023-07-20 14:32 ` Mauricio Faria de Oliveira
2023-07-17 19:16 ` [PATCH RESEND 2/2] loop: do not enforce max_loop hard limit by (new) default Mauricio Faria de Oliveira
2023-07-20 8:31 ` Christoph Hellwig
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=ZLjwrNntqIEb7QQe@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=isaacmanjarres@google.com \
--cc=linux-block@vger.kernel.org \
--cc=mfo@canonical.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).