linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: amit karwar <amitkarwar@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	Amitkumar Karwar <amit.karwar@redpinesignals.com>
Subject: Re: [PATCH 2/6] rsi: use enum for FSM states
Date: Wed, 14 Jun 2017 12:13:22 +0300	[thread overview]
Message-ID: <87zidb2aq5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAEhWJFmzEotu+MpKaHqtXFnWyQWsekk23+Pj-3z8oEVmy2Z2DQ@mail.gmail.com> (amit karwar's message of "Tue, 13 Jun 2017 20:17:32 +0530")

amit karwar <amitkarwar@gmail.com> writes:

> On Tue, Jun 13, 2017 at 12:17 PM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Amitkumar Karwar <amitkarwar@gmail.com> writes:
>>
>>> Currently macros are used for FSM states. We will replace
>>> it with enum so that new state can be added easily without
>>> worrying about macro value.
>>>
>>> Signed-off-by: Amitkumar Karwar <amit.karwar@redpinesignals.com>
>>
>> From and Signed-off-by does not match (gmail.com vs redpinesignals.com).
>> I suggest that you add a separate From line to the commit log containing
>> redpinesignals.com, this way you can still submit patches via gmail.com.
>
> Sure. I will follow this for my future patches.

Actually please resend this series with matching From and S-o-b. I don't
want to edit From headers myself.

>> Also your name in patchwork is not capitalised (patchwork is idiotic and
>> takes the name from patchwork user data and not from the patch):
>>
>>       [1/6] rsi: add usb RS9113 chipset support 2017-06-02 amit
>> karwar New
>>       [2/6] rsi: use enum for FSM states 2017-06-02 amit karwar New
>>       [3/6] rsi: Register interrupt handler before firmware load
>> 2017-06-02 amit karwar New
>>       [4/6] rsi: receive path enhancement for RS9113 2017-06-02 amit
>> karwar New
>>       [5/6] rsi: configure new boot parameters to device 2017-06-02
>> amit karwar New
>>       [6/6] rsi: add tx frame for common device configuration
>> 2017-06-02 amit karwar New
>>
>> To fix that could you please register to patchwork and capitalise your
>> name correctly? You have only one chance, patchwork doesn't allow users
>> edit the name afterwards, so don't do any typos :)
>
> Thanks. I have registered with patchwork and corrected my name.

What address did you use? Patchwork still shows your name all lower:

https://patchwork.kernel.org/project/linux-wireless/list/?submitter=173645

I suspect you didn't register with gmail.com, but with some other
address. I recommend that you link all your email addresses, including
gmail.com, to the same patchwork account and hopefully that fixes it.
You should be able to do that from the profile page in patchwork.

-- 
Kalle Valo

  reply	other threads:[~2017-06-14  9:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 14:12 [PATCH 0/6] rsi driver bringup changes Amitkumar Karwar
2017-06-02 14:13 ` [PATCH 1/6] rsi: add usb RS9113 chipset support Amitkumar Karwar
2017-06-02 14:13 ` [PATCH 2/6] rsi: use enum for FSM states Amitkumar Karwar
2017-06-13  6:47   ` Kalle Valo
2017-06-13 14:47     ` amit karwar
2017-06-14  9:13       ` Kalle Valo [this message]
2017-06-14 14:25         ` Amitkumar Karwar
2017-06-15 14:44           ` Kalle Valo
2017-06-16 15:02             ` Amitkumar Karwar
2017-06-19 15:19               ` Kalle Valo
2017-06-20 13:26                 ` Amitkumar Karwar
2017-06-02 14:13 ` [PATCH 3/6] rsi: Register interrupt handler before firmware load Amitkumar Karwar
2017-06-02 14:13 ` [PATCH 4/6] rsi: receive path enhancement for RS9113 Amitkumar Karwar
2017-06-02 14:13 ` [PATCH 5/6] rsi: configure new boot parameters to device Amitkumar Karwar
2017-06-02 14:13 ` [PATCH 6/6] rsi: add tx frame for common device configuration Amitkumar Karwar
2017-06-14  9:04   ` Kalle Valo
2017-06-14 14:17     ` Amitkumar Karwar
2017-06-14  9:07   ` Kalle Valo
2017-06-14 14:18     ` Amitkumar Karwar

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=87zidb2aq5.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=amit.karwar@redpinesignals.com \
    --cc=amitkarwar@gmail.com \
    --cc=linux-wireless@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).