linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Mark Brown <broonie@kernel.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: intel: remove unused variable
Date: Wed, 02 Mar 2016 21:33:13 +0530	[thread overview]
Message-ID: <56D70EC1.6020807@gmail.com> (raw)
In-Reply-To: <20160302132024.GO18327@sirena.org.uk>

On Wednesday 02 March 2016 06:50 PM, Mark Brown wrote:
> On Wed, Mar 02, 2016 at 12:27:09PM +0000, One Thousand Gnomes wrote:
>> Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
>
>>> My From: is Sudip Mukherjee <sudipm.mukherjee@gmaill.com>
>>> and my Signed-off-by: is Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
>
>>> My From name and Signed-off name matches. But my emails donot match.
>
>> Which is fine - unless you are submitting patches to Mark 8). I also
>> usually split my email address and GregKH doesn't seem to mind at all.
>
> I usually end up applying but I don't like having to think about it and
> normally only for people I recognise both addresses and all the names
> for - there's a lot of places that can fall over.

I was suspecting that since this is a new email address so you objected 
whereas you have seen my vectorindia email many times so you got used to 
it. :)
Let me use my new email address the way I was using my old address and 
you will see its same "me".

> I've noticed an
> increase in the number of people missing out signoffs recently for some
> reason so anything that looks like a non-author message is a red flag.
>
>> The other option I suppose would be to put both addresses in the signed
>> off by sequence, but that probably causes confusion
>
> The other option is to just not use the work address if you don't want
> to use it (that's what I do).

Since I use my work resources and office working hours to generate and 
submit patches so I think I should use my work address as signoff.

regards
sudip

      parent reply	other threads:[~2016-03-02 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 17:23 [PATCH] ASoC: intel: remove unused variable Sudip Mukherjee
2016-03-01  2:59 ` Mark Brown
2016-03-01  5:49   ` Sudip Mukherjee
2016-03-01  7:39     ` [alsa-devel] " Takashi Iwai
2016-03-02  1:02     ` Mark Brown
2016-03-02  6:26       ` Sudip Mukherjee
2016-03-02 10:56         ` Mark Brown
2016-03-02 12:27         ` One Thousand Gnomes
2016-03-02 13:07           ` Sudip Mukherjee
2016-03-02 13:42             ` Mark Brown
2016-03-02 13:20           ` Mark Brown
2016-03-02 13:53             ` One Thousand Gnomes
2016-03-02 14:04               ` Mark Brown
2016-03-02 16:03             ` Sudip Mukherjee [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=56D70EC1.6020807@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /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).