From: Mark Brown <broonie@kernel.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
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, 2 Mar 2016 22:20:24 +0900 [thread overview]
Message-ID: <20160302132024.GO18327@sirena.org.uk> (raw)
In-Reply-To: <20160302122709.0620419f@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
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'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).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-02 13:20 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 [this message]
2016-03-02 13:53 ` One Thousand Gnomes
2016-03-02 14:04 ` Mark Brown
2016-03-02 16:03 ` Sudip Mukherjee
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=20160302132024.GO18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sudipm.mukherjee@gmail.com \
--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