From: Greg KH <gregkh@linuxfoundation.org>
To: Ke Liu <liuke94@huawei.com>
Cc: scott.branden@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, arnd@arndb.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: bcm-vk: Directly use ida_alloc()/free()
Date: Wed, 8 Jun 2022 07:31:32 +0200 [thread overview]
Message-ID: <YqA0NGXzOCnoFVN3@kroah.com> (raw)
In-Reply-To: <20220608031927.1704412-1-liuke94@huawei.com>
On Wed, Jun 08, 2022 at 03:19:27AM +0000, Ke Liu wrote:
> Use ida_alloc()/ida_free() instead of deprecated
> ida_simple_get()/ida_simple_remove().
>
> Signed-off-by: Ke Liu <liuke94@huawei.com>
> ---
> drivers/misc/bcm-vk/bcm_vk_dev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/misc/bcm-vk/bcm_vk_dev.c b/drivers/misc/bcm-vk/bcm_vk_dev.c
> index a16b99bdaa13..a3a82ebbc699 100644
> --- a/drivers/misc/bcm-vk/bcm_vk_dev.c
> +++ b/drivers/misc/bcm-vk/bcm_vk_dev.c
> @@ -1401,7 +1401,7 @@ static int bcm_vk_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> bcm_vk_tty_set_irq_enabled(vk, i);
> }
>
> - id = ida_simple_get(&bcm_vk_ida, 0, 0, GFP_KERNEL);
> + id = ida_alloc(&bcm_vk_ida, GFP_KERNEL);
> if (id < 0) {
> err = id;
> dev_err(dev, "unable to get id\n");
> @@ -1500,7 +1500,7 @@ static int bcm_vk_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> misc_device->name = NULL;
>
> err_ida_remove:
> - ida_simple_remove(&bcm_vk_ida, id);
> + ida_free(&bcm_vk_ida, id);
>
> err_irq:
> for (i = 0; i < vk->num_irqs; i++)
> @@ -1573,7 +1573,7 @@ static void bcm_vk_remove(struct pci_dev *pdev)
> if (misc_device->name) {
> misc_deregister(misc_device);
> kfree(misc_device->name);
> - ida_simple_remove(&bcm_vk_ida, vk->devid);
> + ida_free(&bcm_vk_ida, vk->devid);
If conversions were this simple, why wouldn't the maintainer have done
this already for the whole tree?
Are you sure these types of changes are correct? How did you test them?
thanks,
greg k-h
prev parent reply other threads:[~2022-06-08 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 3:19 Ke Liu
2022-06-08 5:31 ` Greg KH [this message]
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=YqA0NGXzOCnoFVN3@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuke94@huawei.com \
--cc=scott.branden@broadcom.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
all inboxes | Powered by JetHome®