From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, libertas-dev@lists.infradead.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Fixing full name in patchwork
Date: Tue, 8 Dec 2015 10:24:04 +0530 [thread overview]
Message-ID: <20151208045404.GB23610@sudip-pc> (raw)
In-Reply-To: <87zixmb0fp.fsf@kamboji.qca.qualcomm.com>
On Mon, Dec 07, 2015 at 08:03:54PM +0200, Kalle Valo wrote:
> Hi Sudip,
>
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
>
> > We were dereferencing cmd first and checking for NULL later. Lets first
> > check for NULL.
> >
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
>
> I noticed that your name in git log is not your full name:
>
> commit 0a38c8e1b592c16d959da456f425053e323a5153
> Author: sudip <sudipm.mukherjee@gmail.com>
> Date: Tue Nov 24 13:51:38 2015 +0530
>
> This is because for some reason in patchwork your fullname is just
> "sudip":
>
> https://patchwork.kernel.org/patch/7688171/
>
> Could you please fix your name in patchwork so that in the future we can
> use your correct full name? The problem is that I don't know exactly how
> to do this but it should be possible because I remember someone else
> having a similar problem and he was able to fix it.
Hi Kalle,
I have also noticed the patch. Anyway, I have created a profile in
patchwork and given full name. Hopefully that should solve the problem.
regards
sudip
next prev parent reply other threads:[~2015-12-08 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 12:32 [PATCH] libertas: fix possible NULL dereference Sudip Mukherjee
2015-11-23 23:43 ` Andy Shevchenko
2015-11-24 7:32 ` Sudip Mukherjee
2015-12-07 18:03 ` Fixing full name in patchwork Kalle Valo
2015-12-08 4:54 ` Sudip Mukherjee [this message]
2015-12-08 7:54 ` Kalle Valo
2015-12-08 8:21 ` Sudip Mukherjee
2015-12-08 8:30 ` Kalle Valo
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=20151208045404.GB23610@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).