From: Kirill Marinushkin <kmarinushkin@birdec.tech>
To: Rob Herring <robh@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.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 08:04:34 +0100 [thread overview]
Message-ID: <7cbf1452-354f-07d6-2310-cadc4358433e@birdec.tech> (raw)
In-Reply-To: <20181204214313.GA7847@bogus>
Thank you Rob,
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
Best Regards,
Kirill
On 12/04/18 22:43, Rob Herring wrote:
> On Thu, 15 Nov 2018 08:12:53 +0100, Kirill Marinushkin wrote:
>> Output of pcm3060 codec may be configured as single-ended or differential
>>
>> Signed-off-by: Kirill Marinushkin <kmarinushkin@birdec.tech>
>> Cc: devicetree@vger.kernel.org
>> ---
>> Hello Mark,
>>
>> yesterday there was a misunderstanding: when I wrote you
>>
>>> I think you forgot one patch in the series
>>
>> you accidently applied the already-applied patch instead of the forgotten
>> one. To avoid the confusion, in this e-mail I resend you the proper
>> forgotten patch in a separate mailing thread.
>>
>> Please apply this patch for-next.
>>
>> Best Regards,
>> Kirill
>> ---
>> Documentation/devicetree/bindings/sound/pcm3060.txt | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>
> Reviewed-by: Rob Herring <robh@kernel.org>
>
next prev parent reply other threads:[~2018-12-05 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 7:12 Kirill Marinushkin
2018-12-04 21:43 ` Rob Herring
2018-12-05 7:04 ` Kirill Marinushkin [this message]
2018-12-05 15:28 ` Rob Herring
2018-12-05 15:42 ` 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=7cbf1452-354f-07d6-2310-cadc4358433e@birdec.tech \
--to=kmarinushkin@birdec.tech \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--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
all inboxes | Powered by JetHome®