Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     Andrew Morton <akpm@linux-foundation.org>,
        Ken Chen <kenchen@google.com>,
        "Isaac J. Manjarres" <isaacmanjarres@google.com>
Cc:     Saravana Kannan <saravanak@google.com>, stable@vger.kernel.org,
        kernel-team@android.com, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org
In-Reply-To: <20221208212902.765781-1-isaacmanjarres@google.com>
References: <20221208212902.765781-1-isaacmanjarres@google.com>
Subject: Re: [PATCH RESEND v1] loop: Fix the max_loop commandline argument
 treatment when it is set to 0
Message-Id: <167104053516.12018.3829902997304947122.b4-ty@kernel.dk>
Date:   Wed, 14 Dec 2022 10:55:35 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


On Thu, 08 Dec 2022 13:29:01 -0800, Isaac J. Manjarres wrote:
> Currently, the max_loop commandline argument can be used to specify how
> many loop block devices are created at init time. If it is not
> specified on the commandline, CONFIG_BLK_DEV_LOOP_MIN_COUNT loop block
> devices will be created.
> 
> The max_loop commandline argument can be used to override the value of
> CONFIG_BLK_DEV_LOOP_MIN_COUNT. However, when max_loop is set to 0
> through the commandline, the current logic treats it as if it had not
> been set, and creates CONFIG_BLK_DEV_LOOP_MIN_COUNT devices anyway.
> 
> [...]

Applied, thanks!

[1/1] loop: Fix the max_loop commandline argument treatment when it is set to 0
      commit: 85c50197716c60fe57f411339c579462e563ac57

Best regards,
-- 
Jens Axboe