From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Florian Meier <florian.meier@koalo.de>
Subject: Re: [PATCH] ASoC: bcm: Remove obsoleted Kconfig dependency
Date: Thu, 9 Jan 2014 10:32:01 +0000 [thread overview]
Message-ID: <20140109103201.GC31886@sirena.org.uk> (raw)
In-Reply-To: <s5h8uuppt1u.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]
On Thu, Jan 09, 2014 at 07:29:01AM +0100, Takashi Iwai wrote:
> Mark Brown wrote:
> > get_maintainers *should* also tell you to use @kernel.org, that's what's
> > actually in MAINTAINERS (which should be preferred over git history, or
> > both used) which is where I actually read upstream mail.
> Then the problem is that you committed and signed off with linaro.org
> address in git. If you don't want receive any patches at this
It's getting more common these days, companies want their address to end
up in git but it's not so good for upstream mail for whatever reason
(historically a lot of it has been Exchange related, though that's not
the case for me). It's more noticable for people applying patches than
for people sending them.
> address, you should never use it for git. As a Netiquette, one
> shouldn't post a mail to multiple addresses if it's known for the same
> person.
Sure, but if you're going to use one I'd expect the MAINTAINERS address
to win - I did have someone the other day using my Wolfson address still
since they were going off signoffs and the thing they were working on
wasn't that actively developed.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-01-09 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 9:37 [PATCH] ASoC: bcm: Remove obsoleted Kconfig dependency Takashi Iwai
2014-01-08 19:46 ` Florian Meier
2014-01-08 19:59 ` Mark Brown
2014-01-08 20:08 ` Takashi Iwai
2014-01-08 20:17 ` Mark Brown
2014-01-09 6:29 ` Takashi Iwai
2014-01-09 10:32 ` Mark Brown [this message]
2014-01-09 11:00 ` Takashi Iwai
2014-01-09 13:05 ` Mark Brown
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=20140109103201.GC31886@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=florian.meier@koalo.de \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.