From: 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,
Kirill Marinushkin <kmarinushkin@birdec.tech>,
devicetree@vger.kernel.org
Subject: Re: [resend PATCH] dt-bindings: sound: Add documentation for pcm3060 property out-single-ended
Date: Tue, 4 Dec 2018 15:43:13 -0600 [thread overview]
Message-ID: <20181204214313.GA7847@bogus> (raw)
In-Reply-To: <20181115071253.22558-1-kmarinushkin@birdec.tech>
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>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Kirill Marinushkin <kmarinushkin@birdec.tech>
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,
Kirill Marinushkin <kmarinushkin@birdec.tech>,
devicetree@vger.kernel.org
Subject: Re: [resend PATCH] dt-bindings: sound: Add documentation for pcm3060 property out-single-ended
Date: Tue, 4 Dec 2018 15:43:13 -0600 [thread overview]
Message-ID: <20181204214313.GA7847@bogus> (raw)
In-Reply-To: <20181115071253.22558-1-kmarinushkin@birdec.tech>
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-04 21:43 UTC|newest]
Thread overview: 8+ 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-11-15 7:12 ` Kirill Marinushkin
2018-12-04 21:43 ` Rob Herring [this message]
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
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=20181204214313.GA7847@bogus \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kmarinushkin@birdec.tech \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.