From: Mark Brown <broonie@kernel.org>
To: Olof Johansson <olof@lixom.net>
Cc: Felipe Balbi <balbi@ti.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: commit c368e5fc2a190923b786f2de3e79430ea3566a25 regresses MMC
Date: Thu, 21 Nov 2013 20:50:50 +0000 [thread overview]
Message-ID: <20131121205050.GF14725@sirena.org.uk> (raw)
In-Reply-To: <CAOesGMi2wDz2PB7GJbfg3i4bRU+qgT+ubTa+WurQ96biyjaLsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Thu, Nov 21, 2013 at 12:27:06PM -0800, Olof Johansson wrote:
> If you have one email address listed in MAINTAINERS, and do all your
> actual work with another identity, you might want to look at your
> workflow a bit. I suggest either signing off with the MAINTAINERS
The only thing that uses the work address is patches and signoffs, all
my e-mail traffic is done from my kernel.org address (including patch
posts).
> email address, or changing the entries of that file. People should
> expect to be able to email you on the address you sign off with.
Unfortunately my employer can't cope with that at present and I don't
really want to use my work address for everything since all the stuff
from upstream DoSs the stuff that pays the bills. I wouldn't mind if
people mailed both, but if you're going to pick a single one then the
one listed in MAINTAINERS is the way forwards (which generally is the
address people manage to pick).
/me notes that he'd probably have been less grumpy if the message had
a subject line that had content in it, even had it gone to the right
mailbox there's a good chance I'd never even have opened the mail due to
that - if anything it going to the wrong place actually worked around
the subject line here.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-21 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 17:58 commit c368e5fc2a190923b786f2de3e79430ea3566a25 regresses MMC Felipe Balbi
2013-11-20 20:34 ` Mark Brown
2013-11-20 20:51 ` Felipe Balbi
2013-11-21 2:48 ` Felipe Balbi
2013-11-21 10:49 ` Mark Brown
2013-11-21 12:58 ` Felipe Balbi
2013-11-21 16:43 ` Stephen Warren
2013-11-21 18:36 ` Mark Brown
2013-11-21 18:44 ` Stephen Warren
2013-11-21 19:28 ` Mark Brown
2013-11-21 20:27 ` Olof Johansson
2013-11-21 20:50 ` Mark Brown [this message]
2013-11-22 1:56 ` Felipe Balbi
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=20131121205050.GF14725@sirena.org.uk \
--to=broonie@kernel.org \
--cc=balbi@ti.com \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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