From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
robh+dt@kernel.org, Jiaxin.Yu@mediatek.com
Subject: Re: [PATCH] ASoC: dt-bindings: mediatek: mt8192: re-add audio afe document
Date: Thu, 26 Aug 2021 16:48:53 +0100 [thread overview]
Message-ID: <YSe35dOicFFDiXAy@sirena.org.uk> (raw)
In-Reply-To: <CA+Px+wWr99PxEz6qROhj7H8LXFiRZ1sxrn-BcB7ZODJA1Suh+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Thu, Aug 26, 2021 at 11:28:15PM +0800, Tzung-Bi Shih wrote:
> On Thu, Aug 26, 2021 at 11:19 PM Mark Brown <broonie@kernel.org> wrote:
> > > The dependency has merged. Re-adds back the document.
> > What is the dependency and where wsa it merged?
> The context is in the original email after "---". Do you think it
> needs to be part of the commit message?
I was looking for a description of what these things are and
where things are in words - I'm on a train with spotty network
access which makes them not as useful as they might be.
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-08-26 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 14:13 [PATCH] ASoC: dt-bindings: mediatek: mt8192: re-add audio afe document Tzung-Bi Shih
2021-08-26 15:11 ` Mark Brown
2021-08-26 15:28 ` Tzung-Bi Shih
2021-08-26 15:48 ` Mark Brown [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=YSe35dOicFFDiXAy@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Jiaxin.Yu@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tzungbi@google.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