From: Timur Tabi <timur@kernel.org>
To: Liang He <windhl@126.com>
Cc: Timur Tabi <timur@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
jirislaby@kernel.org,
PowerPC Mailing List <linuxppc-dev@lists.ozlabs.org>,
linux-serial@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: serial: Fix refcount leak bug in ucc_uart.c
Date: Sat, 18 Jun 2022 12:07:05 -0500 [thread overview]
Message-ID: <CAOZdJXU6R1wma8VXwfPYzq6eSkT84DiXb+3eQCEVanLZC2LQ3w@mail.gmail.com> (raw)
In-Reply-To: <20220618060850.4058525-1-windhl@126.com>
On Sat, Jun 18, 2022 at 1:09 AM Liang He <windhl@126.com> wrote:
>
> In soc_info(), of_find_node_by_type() will return a node pointer
> with refcount incremented. We should use of_node_put() when it is
> not used anymore.
>
> Signed-off-by: Liang He <windhl@126.com>
Acked-by: Timur Tabi <timur@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@kernel.org>
To: Liang He <windhl@126.com>
Cc: Timur Tabi <timur@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
PowerPC Mailing List <linuxppc-dev@lists.ozlabs.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org, jirislaby@kernel.org
Subject: Re: [PATCH] tty: serial: Fix refcount leak bug in ucc_uart.c
Date: Sat, 18 Jun 2022 12:07:05 -0500 [thread overview]
Message-ID: <CAOZdJXU6R1wma8VXwfPYzq6eSkT84DiXb+3eQCEVanLZC2LQ3w@mail.gmail.com> (raw)
In-Reply-To: <20220618060850.4058525-1-windhl@126.com>
On Sat, Jun 18, 2022 at 1:09 AM Liang He <windhl@126.com> wrote:
>
> In soc_info(), of_find_node_by_type() will return a node pointer
> with refcount incremented. We should use of_node_put() when it is
> not used anymore.
>
> Signed-off-by: Liang He <windhl@126.com>
Acked-by: Timur Tabi <timur@kernel.org>
next prev parent reply other threads:[~2022-06-18 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 6:08 [PATCH] tty: serial: Fix refcount leak bug in ucc_uart.c Liang He
2022-06-18 6:08 ` Liang He
2022-06-18 17:07 ` Timur Tabi [this message]
2022-06-18 17:07 ` Timur Tabi
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=CAOZdJXU6R1wma8VXwfPYzq6eSkT84DiXb+3eQCEVanLZC2LQ3w@mail.gmail.com \
--to=timur@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=windhl@126.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.