From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Hillf Danton <hdanton@sina.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
"Reviewed-by : Tyler Hicks" <tyhicks@linux.microsoft.com>,
linux-block@vger.kernel.org
Subject: [PATCH 5/7] loop: remove the unused idx argument to loop_control_get_free
Date: Wed, 18 Aug 2021 08:24:53 +0200 [thread overview]
Message-ID: <20210818062455.211065-6-hch@lst.de> (raw)
In-Reply-To: <20210818062455.211065-1-hch@lst.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/block/loop.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 9176784d4fca..e93baff664c9 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -2486,7 +2486,7 @@ static int loop_control_remove(int idx)
return ret;
}
-static int loop_control_get_free(int idx)
+static int loop_control_get_free(void)
{
struct loop_device *lo;
int id, ret;
@@ -2514,7 +2514,7 @@ static long loop_control_ioctl(struct file *file, unsigned int cmd,
case LOOP_CTL_REMOVE:
return loop_control_remove(parm);
case LOOP_CTL_GET_FREE:
- return loop_control_get_free(parm);
+ return loop_control_get_free();
default:
return -ENOSYS;
}
--
2.30.2
next prev parent reply other threads:[~2021-08-18 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 6:24 sort out the lock order in the loop driver Christoph Hellwig
2021-08-18 6:24 ` [PATCH 1/7] loop: remove the ->ioctl method in loop_func_table Christoph Hellwig
2021-08-18 6:24 ` [PATCH 2/7] loop: return void from the ->release " Christoph Hellwig
2021-08-18 6:24 ` [PATCH 3/7] loop: merge the cryptoloop module into the main loop module Christoph Hellwig
2021-08-18 6:24 ` [PATCH 4/7] loop: devirtualize transfer transformations Christoph Hellwig
2021-08-18 6:24 ` Christoph Hellwig [this message]
2021-08-18 6:24 ` [PATCH 6/7] loop: move loop device deletion out of loop_ctl_mutex Christoph Hellwig
2021-08-18 6:24 ` [PATCH 7/7] loop: avoid holding loop_ctl_mutex over add_disk Christoph Hellwig
2021-08-18 10:08 ` sort out the lock order in the loop driver Tetsuo Handa
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=20210818062455.211065-6-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tyhicks@linux.microsoft.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).