From: Greg KH <gregkh@linuxfoundation.org>
To: Ivan Bakula <wamreu@gmail.com>
Cc: robh@kernel.org, jirislaby@kernel.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TTY: serdev: Replace depricated macros
Date: Thu, 6 May 2021 19:39:45 +0200 [thread overview]
Message-ID: <YJQp4W2X/tuvLfVA@kroah.com> (raw)
In-Reply-To: <20210506183228.33981-1-wamreu@gmail.com>
On Thu, May 06, 2021 at 08:32:28PM +0200, Ivan Bakula wrote:
> Replace depricated macros ida_simple_get and ida_simple_remove with
> appropriate function calls to ida_alloc and ida_free.
>
> Signed-off-by: Ivan Bakula <wamreu@gmail.com>
> ---
> drivers/tty/serdev/core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serdev/core.c b/drivers/tty/serdev/core.c
> index aead0c0c9..5f873960b 100644
> --- a/drivers/tty/serdev/core.c
> +++ b/drivers/tty/serdev/core.c
> @@ -75,7 +75,7 @@ static bool is_serdev_device(const struct device *dev)
> static void serdev_ctrl_release(struct device *dev)
> {
> struct serdev_controller *ctrl = to_serdev_controller(dev);
> - ida_simple_remove(&ctrl_ida, ctrl->nr);
> + ida_free(&ctrl_ida, ctrl->nr);
> kfree(ctrl);
> }
>
> @@ -488,7 +488,7 @@ struct serdev_controller *serdev_controller_alloc(struct device *parent,
> if (!ctrl)
> return NULL;
>
> - id = ida_simple_get(&ctrl_ida, 0, 0, GFP_KERNEL);
> + id = ida_alloc(&ctrl_ida, GFP_KERNEL);
> if (id < 0) {
> dev_err(parent,
> "unable to allocate serdev controller identifier.\n");
> --
> 2.31.1
>
If these really are "deprecated", why not just do a search/replace
across the whole tree and change them? Or if not, what is wrong with
the existing ones?
Why shouldn't we be using the old calls? What is wrong with them?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-06 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 18:32 [PATCH] TTY: serdev: Replace depricated macros Ivan Bakula
2021-05-06 17:39 ` Greg KH [this message]
2021-05-07 11:16 ` Ivan Bakula
2021-05-07 10:51 ` Greg KH
2021-05-07 20:18 ` Ivan Bakula
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=YJQp4W2X/tuvLfVA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wamreu@gmail.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