From: Mark Brown <broonie@kernel.org>
To: Alejandro Tafalla <atafalla@dnyon.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
~postmarketos/upstreaming@lists.sr.ht,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] dt-bindings: sound: max98927: Add reset-gpios optional property
Date: Thu, 7 Oct 2021 15:03:53 +0100 [thread overview]
Message-ID: <YV7+STMCR9VwVwzH@sirena.org.uk> (raw)
In-Reply-To: <5004d52da527bf1dd9e5b17e20b2ce50a0b57b5a.1633572679.git.atafalla@dnyon.com>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
On Thu, Oct 07, 2021 at 04:38:58AM +0200, Alejandro Tafalla wrote:
> Signed-off-by: Alejandro Tafalla <atafalla@dnyon.com>
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:[~2021-10-07 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 2:38 [PATCH v4 0/2] Add reset-gpios handling for max98927 Alejandro Tafalla
2021-10-07 2:38 ` [PATCH v4 1/2] ASoC: max98927: Handle reset gpio when probing i2c Alejandro Tafalla
2021-10-07 2:38 ` [PATCH v4 2/2] dt-bindings: sound: max98927: Add reset-gpios optional property Alejandro Tafalla
2021-10-07 2:44 ` Alejandro Tafalla
2021-10-07 7:06 ` Andy Shevchenko
2021-10-07 9:47 ` Alejandro Tafalla
2021-10-07 14:03 ` Mark Brown [this message]
2021-10-07 21:37 ` [PATCH v4 0/2] Add reset-gpios handling for max98927 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=YV7+STMCR9VwVwzH@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andy.shevchenko@gmail.com \
--cc=atafalla@dnyon.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).