From: Paul Kocialkowski <contact@paulk.fr>
To: Mark Brown <broonie@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: alsa-devel@alsa-project.org, Stephen Warren <swarren@nvidia.com>,
Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] sound: ASoC: tegra: Remove SoC-specific Kconfig depends and selects
Date: Thu, 17 Aug 2017 22:07:56 +0300 [thread overview]
Message-ID: <1502996876.1287.2.camel@paulk.fr> (raw)
In-Reply-To: <20170817142639.ixe7pfzpfhwbhz5q@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1226 bytes --]
Le jeudi 17 août 2017 à 15:26 +0100, Mark Brown a écrit :
> On Thu, Aug 17, 2017 at 04:22:11PM +0200, Thierry Reding wrote:
>
> > do you want to pick this up, or would you rather provide an Acked-by
> > so
> > that I can take it through the Tegra tree along with the defconfig
> > changes? I can provide a branch with this patch in case we ever need
> > it
> > for conflict resolution.
>
> I don't know what this patch is, sorry. I think I probably deleted
> the
> mail since the subject line indicates it's not for me.
>
> 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.
I have just sent out another version with a subject line that matches
what others have been doing (mainly, dropping the "sound:" prefix).
Cheers,
--
Paul Kocialkowski,
developer of free digital technology and hardware support.
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2017-08-17 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 11:22 [PATCH 1/3] sound: ASoC: tegra: Remove SoC-specific Kconfig depends and selects Paul Kocialkowski
2017-07-30 11:22 ` [PATCH 2/3] ARM: configs: Add Tegra I2S interfaces to tegra_defconfig Paul Kocialkowski
[not found] ` <20170730112220.15525-2-contact-W9ppeneeCTY@public.gmane.org>
2017-07-31 10:22 ` Thierry Reding
2017-07-30 11:22 ` [PATCH 3/3] ARM: configs: Add Tegra I2S interfaces to multi_v7_defconfig Paul Kocialkowski
[not found] ` <20170730112220.15525-3-contact-W9ppeneeCTY@public.gmane.org>
2017-07-31 10:22 ` Thierry Reding
[not found] ` <20170730112220.15525-1-contact-W9ppeneeCTY@public.gmane.org>
2017-07-31 10:23 ` [PATCH 1/3] sound: ASoC: tegra: Remove SoC-specific Kconfig depends and selects Thierry Reding
2017-08-17 14:22 ` Thierry Reding
2017-08-17 14:26 ` Mark Brown
2017-08-17 19:07 ` Paul Kocialkowski [this message]
2017-08-18 11:48 ` Applied "ASoC: tegra: Remove SoC-specific Kconfig depends and selects" to the asoc tree 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=1502996876.1287.2.camel@paulk.fr \
--to=contact@paulk.fr \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=swarren@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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).