From: wang xiaolei <xiaolei.wang@windriver.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: l.stach@pengutronix.de, gregkh@linuxfoundation.org,
jirislaby@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de, esben@geanix.com,
marex@denx.de, ilpo.jarvinen@linux.intel.com,
linux@rasmusvillemoes.dk, stefan.eichenberger@toradex.com,
l.sanfilippo@kunbus.com, cniedermaier@dh-electronics.com,
rickaran@axis.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] serial: imx: Use uart_port_lock_irq() instead of uart_port_lock()
Date: Wed, 11 Dec 2024 02:40:39 +1100 [thread overview]
Message-ID: <6ecc80c1-8422-48d5-97f7-dcc0f8d49466@windriver.com> (raw)
In-Reply-To: <CAOMZO5AzNVd_xut2wBBHeyccFdC+1c4p50Uhzo=+BDbV=mEP2g@mail.gmail.com>
On 12/10/24 9:37 PM, Fabio Estevam wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Tue, Dec 10, 2024 at 12:43 AM Xiaolei Wang
> <xiaolei.wang@windriver.com> wrote:
>> When executing 'ehco mem > /sys/power/state', the following
> ehco --> echo
Thanks, I will update the commit log in the next version
thanks
xiaolei
>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
prev parent reply other threads:[~2024-12-10 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 3:42 [PATCH v2] serial: imx: Use uart_port_lock_irq() instead of uart_port_lock() Xiaolei Wang
2024-12-10 9:00 ` Lucas Stach
2024-12-10 10:37 ` Fabio Estevam
2024-12-10 15:40 ` wang xiaolei [this message]
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=6ecc80c1-8422-48d5-97f7-dcc0f8d49466@windriver.com \
--to=xiaolei.wang@windriver.com \
--cc=cniedermaier@dh-electronics.com \
--cc=esben@geanix.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=l.sanfilippo@kunbus.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=marex@denx.de \
--cc=rickaran@axis.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan.eichenberger@toradex.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