From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 김명욱 <mwkim@gaonchips.com>, alsa-devel@alsa-project.org
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Maxim Kochetkov" <fido_max@inbox.ru>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Xingyu Wu" <xingyu.wu@starfivetech.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dwc: fix typo in comment
Date: Tue, 12 Sep 2023 08:34:35 +0700 [thread overview]
Message-ID: <3721e97b-365c-d6da-b8b8-1a963e569e3c@gmail.com> (raw)
In-Reply-To: <gab64ffbd7bdbafc@gaonchips.com>
On 12/09/2023 08:23, 김명욱 wrote:
> ISR_RXFO means "Status of Data Overrun interrupt for the RX channel" according to the datasheet.
>
> So, the comment should be RX, not TX
>
=
OK, but next time don't reply like:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
because I can't see the context you're replying to.
And don't send HTML emails as mailing lists hate and
block them.
Regardless, send v2 with reviews (especially on patch description like this)
addressed.
Thanks!
--
An old man doll... just what I always wanted! - Clara
next parent reply other threads:[~2023-09-12 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gab64ffbd7bdbafc@gaonchips.com>
2023-09-12 1:34 ` Bagas Sanjaya [this message]
2023-09-11 6:46 Myunguk Kim
2023-09-11 8:25 ` Maxim Kochetkov
2023-09-11 12:45 ` Bagas Sanjaya
2023-09-12 13:34 ` Mark Brown
2023-09-13 2:28 ` Myunguk Kim
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=3721e97b-365c-d6da-b8b8-1a963e569e3c@gmail.com \
--to=bagasdotme@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fido_max@inbox.ru \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwkim@gaonchips.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=xingyu.wu@starfivetech.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
all inboxes | Powered by JetHome®