From: George Song <George.Song@maximintegrated.com>
To: Rob Herring <robh@kernel.org>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"george.song@analog.com" <george.song@analog.com>,
Steve Lee <SteveS.Lee@maximintegrated.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Ryan Lee <RyanS.Lee@maximintegrated.com>
Subject: RE: [EXTERNAL] Re: [v5 1/2] ASoC: dt-bindings: max98520: add initial bindings
Date: Mon, 25 Oct 2021 07:21:06 +0000 [thread overview]
Message-ID: <BYAPR11MB367174F7CBA3ADEB98B64489F4839@BYAPR11MB3671.namprd11.prod.outlook.com> (raw)
In-Reply-To: <YXNLJkzWTBoqVa1n@robh.at.kernel.org>
> On Wed, 20 Oct 2021 17:30:54 +0900, George Song wrote:
> > add initial bindings for max98520 audio amplifier
> >
> > Signed-off-by: George Song <george.song@maximintegrated.com>
> > ---
> > .../bindings/sound/maxim,max98520.yaml | 36
> +++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/sound/maxim,max98520.yaml
> >
>
>
> Please add Acked-by/Reviewed-by tags when posting new versions.
> However, there's no need to repost patches *only* to add the tags.
> The upstream maintainer will do that for acks received on the
> version they apply.
>
> If a tag was not added on purpose, please state why and what changed.
OK I`ll add Reviewed-by tag which is remained from you in v3 patch
as "Reviewed-by: Rob Herring <robh@kernel.org>"
prev parent reply other threads:[~2021-10-25 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 8:30 George Song
2021-10-22 23:37 ` Rob Herring
2021-10-25 7:21 ` George Song [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=BYAPR11MB367174F7CBA3ADEB98B64489F4839@BYAPR11MB3671.namprd11.prod.outlook.com \
--to=george.song@maximintegrated.com \
--cc=RyanS.Lee@maximintegrated.com \
--cc=SteveS.Lee@maximintegrated.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.song@analog.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
/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®