linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yfw <fengwei.yin@linaro.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	wcn36xx@lists.infradead.org, Bob Copeland <me@bobcopeland.com>,
	linux-wireless@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>,
	k.eugene.e@gmail.com
Subject: Re: [PATCH] wcn36xx: Remove warning message when dev is NULL for arm64 dma_alloc.
Date: Fri, 30 Oct 2015 05:49:25 +0000	[thread overview]
Message-ID: <20151030054923.GA11592@gmail.com> (raw)
In-Reply-To: <874mh9ne7x.fsf@kamboji.qca.qualcomm.com>

On Fri, Oct 30, 2015 at 06:59:46AM +0200, Kalle Valo wrote:
> Nicolas Dechesne <nicolas.dechesne@linaro.org> writes:
> 
> > On Fri, Oct 30, 2015 at 12:34 AM, fengwei.yin <fengwei.yin@linaro.org> wrote:
> >>>>
> >>>>
> >>>> Please fix your name. I don't know why but your name in git statistics
> >>>> is now "yfw":
> >>>>
> >>>> yfw (1):
> >>>>        wcn36xx: Remove warning message when dev is NULL for arm64 dma_alloc.
> >>>>
> >>>> The right format for both From header and Signed-off-by line is:
> >>>>
> >>>> First Lastname <username@example.com>
> >>>>
> >>>
> >>> It looks like everything is fine in my side. Could you please check your
> >>> .mailmap whether the email was mapped to "yfw"?
> >>
> >>                    ~~~~~~~~~~ typo fix: "my email address"
> >
> > fwiw.. I applied the original patch from the list locally, and I don't
> > see this issue after git am <file>:
> >
> > $ git shortlog -1
> > Yin, Fengwei (1):
> >       wcn36xx: Remove warning message when dev is NULL for arm64 dma_alloc.
> 
> Ah, I think it's coming from patchwork:
> 
> "Submitter	yfw"
> 
> https://patchwork.kernel.org/patch/7484791/
> 
> Fengwei, please fix your name in patchwork. It should be easy to do.
Kalle, any clue about how to change the name in patchwork? I can't find
how on the patchwork website.

> 
> Anyway, my original comment still stands. The correct format for name
> is:
> 
>         Random J Developer <random@developer.example.org>
> 
> NOT:
> 
>         Developer, Random J <random@developer.example.org>
> 
> See SubmittingPatches.
Will update the patch. Thanks.

Regards
Yin, Fengwei

> 
> -- 
> Kalle Valo

  reply	other threads:[~2015-10-30  5:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26  2:36 [PATCH] wcn36xx: Remove warning message when dev is NULL for arm64 dma_alloc Yin, Fengwei
2015-10-26 18:24 ` Bjorn Andersson
2015-10-27  0:06   ` yfw
2015-10-28  8:21     ` Eugene Krasnikov
2015-10-28 18:59 ` Kalle Valo
2015-10-29 20:01 ` [PATCH] " Kalle Valo
2015-10-29 23:32   ` fengwei.yin
2015-10-29 23:34     ` fengwei.yin
2015-10-29 23:41       ` Nicolas Dechesne
2015-10-30  4:59         ` Kalle Valo
2015-10-30  5:49           ` yfw [this message]
2015-10-30  6:02             ` Kalle Valo
2015-10-30  6:05               ` fengwei.yin
2015-10-30  6:41               ` fengwei.yin

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=20151030054923.GA11592@gmail.com \
    --to=fengwei.yin@linaro.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=k.eugene.e@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=wcn36xx@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).