From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Claudiu <claudiu.beznea@tuxon.dev>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
tony@atomide.com, l.sanfilippo@kunbus.com, tglx@linutronix.de,
geert+renesas@glider.be, ulf.hansson@linaro.org,
peng.fan@nxp.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, linux-pm@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [RFT PATCH v2] serial: core: Call device_set_awake_path() for console port
Date: Thu, 25 Apr 2024 12:51:25 +0300 [thread overview]
Message-ID: <Zionncg1uUAb9BDP@smile.fi.intel.com> (raw)
In-Reply-To: <ZionWJ7ods60zuYX@smile.fi.intel.com>
On Thu, Apr 25, 2024 at 12:50:16PM +0300, Andy Shevchenko wrote:
> On Thu, Apr 25, 2024 at 10:09:36AM +0300, Claudiu wrote:
> > From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
...
> > [1] https://elixir.bootlin.com/linux/v6.9-rc5/source/drivers/pmdomain/renesas/rmobile-sysc.c#L116
> > [2] https://elixir.bootlin.com/linux/v6.9-rc5/source/drivers/pmdomain/imx/scu-pd.c#L357
>
> No need to have the HTTP links into the kernel sources, you may simply refer to
> the files in the source tree.
>
> [1] drivers/pmdomain/renesas/rmobile-sysc.c:L116
> [2] drivers/pmdomain/imx/scu-pd.c:L357
Should be without 'L' to follow the `git grep -n` output format.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-25 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 7:09 [RFT PATCH v2] serial: core: Call device_set_awake_path() for console port Claudiu
2024-04-25 7:48 ` Geert Uytterhoeven
2024-04-25 9:50 ` Andy Shevchenko
2024-04-25 9:51 ` Andy Shevchenko [this message]
2024-04-26 15:11 ` Tony Lindgren
2024-04-25 16:39 ` Ulf Hansson
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=Zionncg1uUAb9BDP@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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 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.