mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugo Villeneuve <hugo@hugovil.com>
To: Xiangwu Lai <laixiangwu@cmss.chinamobile.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: sc16is7xx: Fix clock leak on invalid clock frequency
Date: Thu, 12 Nov 2026 16:33:45 -0500	[thread overview]
Message-ID: <20261112163345.a88ea8ac42f58d1a38c3e069@hugovil.com> (raw)
In-Reply-To: <20261112021335.1774-1-laixiangwu@cmss.chinamobile.com>

Hi,

On Thu, 12 Nov 2026 10:13:34 +0800
Xiangwu Lai <laixiangwu@cmss.chinamobile.com> wrote:

> Hi Greg,
> 
> sorry for the missing context.  The patch I was pinging is:
> 
>   serial: sc16is7xx: Fix clock leak on invalid clock frequency
>   https://lore.kernel.org/all/20261030085508.1882-1-laixiangwu@cmss.chinamobile.com/
> 
> sc16is7xx_probe() enables the clock with clk_prepare_enable() early
> in the probe path.  If the clock frequency cannot be determined
> (neither from the clock itself, nor from the "clock-frequency"
> property or platform data), the driver bails out with -EINVAL
> without disabling the clock again, while the later error paths of
> the probe already jump to the out_clk label.  The patch makes this
> error path jump to out_clk as well, so the clock is disabled like
> on the other error paths.

It is better to simply reply to the original email, to have the full
context, without having to click on a link to see the original message.

> 
> It was submitted on Oct 30.  Is there anything blocking it, or does
> it just need more time?

I'll reply in the original email...

-- 
Hugo Villeneuve

  reply	other threads:[~2026-11-12 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30  8:55 laixiangwu
2026-11-11  9:52 ` Xiangwu Lai
2026-11-11 13:16   ` Greg Kroah-Hartman
2026-11-12  2:13     ` Xiangwu Lai
2026-11-12 21:33       ` Hugo Villeneuve [this message]
2026-11-12 21:39 ` Hugo Villeneuve
2026-11-13 10:37   ` Xiangwu Lai
2026-11-13 16:58     ` Hugo Villeneuve

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=20261112163345.a88ea8ac42f58d1a38c3e069@hugovil.com \
    --to=hugo@hugovil.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=laixiangwu@cmss.chinamobile.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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®