From: Mark Brown <broonie@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: YC Hung <yc.hung@mediatek.com>, Rob Herring <robh@kernel.org>,
robh+dt@kernel.org, daniel.baluta@nxp.com,
trevor.wu@mediatek.com, tiwai@suse.com,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
cezary.rojewski@intel.com, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
allen-kh.cheng@mediatek.com
Subject: Re: [PATCH v4] dt-bindings: dsp: mediatek: add mt8195 dsp document
Date: Fri, 29 Apr 2022 14:19:43 +0100 [thread overview]
Message-ID: <Ymvl7x9NTJor/vfx@sirena.org.uk> (raw)
In-Reply-To: <cf9b425e-84ff-af12-72a7-4056b8cbf90d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Fri, Apr 29, 2022 at 02:57:12PM +0200, Matthias Brugger wrote:
> On 29/04/2022 07:59, YC Hung wrote:
> > Sorry I miss this mail.
> > Could you please help to check this patch? Thanks.
> Rob gave his reviewed-by. I just saw that the driver maintainer is Mark, so
> I expect him to take the patch through his tree. Didn't realized this
> beforehand.
TBH I'd missed this since there was nothing in the subject line that
drew my attention to it. Seen it now though.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-29 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 6:48 [PATCH v4] dt-bindings: dsp: mediatek: add mt8195 dsp document YC Hung
2022-01-12 1:43 ` Rob Herring
2022-01-14 12:56 ` Matthias Brugger
2022-04-29 5:59 ` YC Hung
2022-04-29 12:57 ` Matthias Brugger
2022-04-29 13:19 ` Mark Brown [this message]
2022-04-29 15:02 ` Mark Brown
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=Ymvl7x9NTJor/vfx@sirena.org.uk \
--to=broonie@kernel.org \
--cc=allen-kh.cheng@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
--cc=trevor.wu@mediatek.com \
--cc=yc.hung@mediatek.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;
as well as URLs for NNTP newsgroup(s).