From: George Song <George.Song@maximintegrated.com>
To: Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"george.song@analog.com" <george.song@analog.com>,
Ryan Lee <RyanS.Lee@maximintegrated.com>,
Steve Lee <SteveS.Lee@maximintegrated.com>
Subject: RE: [EXTERNAL] Re: [v2 1/2] ASoC: dt-bindings: max98520: changed signed-off-by email address
Date: Mon, 18 Oct 2021 04:27:56 +0000 [thread overview]
Message-ID: <BYAPR11MB36713FD5504CA0200F00250DF4BC9@BYAPR11MB3671.namprd11.prod.outlook.com> (raw)
In-Reply-To: <YWmxd/tnHRXUEAxy@sirena.org.uk>
> On Fri, Oct 15, 2021 at 04:27:08PM +0900, George Song wrote:
> > changed signed-off-by email address to maximintegrated group.
> >
> > Signed-off-by: George Song <george.song@maximintegrated.com>
> > ---
> > Documentation/devicetree/bindings/sound/maxim,max98520.yaml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> This file isn't upstream - it looks like you've sent an incremental patch
> against a previous posting instead of revising your patch? Once a patch
> is accepted upstream you should send incremental changes but until then
> you should repost the whole thing.
OK I see. I`ll re send patch including whole things.
prev parent reply other threads:[~2021-10-18 4:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 7:27 George Song
2021-10-15 7:27 ` [v2 2/2] ASoC: max98520: modified alignment and blank George Song
2021-10-15 16:51 ` Mark Brown
2021-10-18 4:28 ` [EXTERNAL] " George Song
2021-10-15 16:51 ` [v2 1/2] ASoC: dt-bindings: max98520: changed signed-off-by email address Mark Brown
2021-10-18 4:27 ` 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=BYAPR11MB36713FD5504CA0200F00250DF4BC9@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 \
/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®