From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Kirill Marinushkin <kmarinushkin@birdec.tech>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [resend PATCH] dt-bindings: sound: Add documentation for pcm3060 property out-single-ended
Date: Wed, 5 Dec 2018 15:42:29 +0000 [thread overview]
Message-ID: <20181205154229.GG6205@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqLirgcDwANbORiez0xtO1tEHDL-O8XdbZSP6R+WZF_HLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Wed, Dec 05, 2018 at 09:28:51AM -0600, Rob Herring wrote:
> On Wed, Dec 5, 2018 at 1:02 AM Kirill Marinushkin
> > Mark already applied this patch, with a slightly modified subject:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-next&id=fd7de6370cb62b147185834d60069568a21acacd
> Humm, I wonder why I didn't have Mark's "Applied ..." email for it?
> Otherwise, my scripts rely on the subject matching which breaks when
> maintainers edit subjects.
Probably due to some problem contacting patchwork, the CC list comes
from patchwork so if that (or the network to it) is unstable then the
scripts can't get anything that's not in the actual commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-12-05 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 7:12 [resend PATCH] dt-bindings: sound: Add documentation for pcm3060 property out-single-ended Kirill Marinushkin
2018-12-04 21:43 ` Rob Herring
2018-12-05 7:04 ` Kirill Marinushkin
2018-12-05 15:28 ` Rob Herring
2018-12-05 15:42 ` 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=20181205154229.GG6205@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=kmarinushkin@birdec.tech \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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