linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 linux-serial <linux-serial@vger.kernel.org>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] serial: 8250_dw: Emit an error message if getting the baudclk failed
Date: Thu, 22 Feb 2024 15:48:48 +0200 (EET)	[thread overview]
Message-ID: <3dca13d5-6ee4-e417-577f-79a5b16eb469@linux.intel.com> (raw)
In-Reply-To: <rxbnydqttxdduseprrnugirdvndznbfpi3q2nxctxdelhoc6t6@7aj4jmzvorv4>

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

On Thu, 22 Feb 2024, Uwe Kleine-König wrote:
> On Thu, Feb 22, 2024 at 01:50:40PM +0200, Ilpo Järvinen wrote:
> > On Thu, 22 Feb 2024, Uwe Kleine-König wrote:
> > 
> > > Instead of silently giving up, at least tell what the problem is.
> > > 
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > ---
> > >  drivers/tty/serial/8250/8250_dw.c | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
> > > index 2d1f350a4bea..94aa3dddb71e 100644
> > > --- a/drivers/tty/serial/8250/8250_dw.c
> > > +++ b/drivers/tty/serial/8250/8250_dw.c
> > > @@ -597,7 +597,8 @@ static int dw8250_probe(struct platform_device *pdev)
> > >  	if (data->clk == NULL)
> > >  		data->clk = devm_clk_get_optional_enabled(dev, NULL);
> > >  	if (IS_ERR(data->clk))
> > > -		return PTR_ERR(data->clk);
> > > +		return dev_err_probe(dev, PTR_ERR(data->clk),
> > > +				     "failed to get baudclk\n");
> > 
> > Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> 
> Thanks. Is the expectation now with your tag that Greg (added to Cc:)
> picks up this patch? 

Yes, Greg handles applying serial patches. There's just too low volume of 
patches for it be useful for me to setup some an intermediate tree for 
8250_dw/lpss only.

-- 
 i.

  reply	other threads:[~2024-02-22 13:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 11:19 [PATCH] serial: 8250_dw: Emit an error message if getting the baudclk failed Uwe Kleine-König
2024-02-22 11:50 ` Ilpo Järvinen
2024-02-22 13:36   ` Uwe Kleine-König
2024-02-22 13:48     ` Ilpo Järvinen [this message]
2024-02-22 14:24       ` Uwe Kleine-König
2024-02-22 15:10     ` Andy Shevchenko
2024-02-22 15:11 ` Andy Shevchenko
2024-02-22 18:37   ` Uwe Kleine-König
2024-02-26 16:00 ` VAMSHI GAJJELA
2024-02-26 16:37   ` Andy Shevchenko
2024-02-28 17:45     ` VAMSHI GAJJELA
2024-02-28 17:59       ` Andy Shevchenko

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=3dca13d5-6ee4-e417-577f-79a5b16eb469@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).