From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: ASoC: samsung: MACH_SMDK6450
Date: Fri, 4 Jul 2014 12:45:05 +0100 [thread overview]
Message-ID: <20140704114505.GA19453@sirena.org.uk> (raw)
In-Reply-To: <4203198.qV4EZfpui2@wuerfel>
On Fri, Jul 04, 2014 at 11:01:52AM +0200, Arnd Bergmann wrote:
> On Thursday 03 July 2014 20:39:41 Olof Johansson wrote:
> > On Thu, Jul 3, 2014 at 5:39 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > Mark is the _only_ linux developer in the world who will give you crap
> > for sending him patches to the very same email that he signs off all
> > his work with.
> > I really wish Linaro would just let him sign off with his
> > long-standing kernel.org email address instead so the rest of us
> > wouldn't have to keep track of this.
Me too, it's a constant source of aggrivation.
> FWIW David Miller has a similar policy: he only applies networking
> patches that are sent to the netdev mailing list. This seems like
> a good idea in general (to ensure they are getting exposed to the
> public).
Right, I do tend to insist on this as well (I also think some other
patchwork users do this as well as davem, things need to hit the list to
go into patchwork), plus including comaintainers where that's relevant.
For the most part anything that ends up going to the work address also
has one of those problems.
> Mark, any chance we could convince to pick up patches from
> alsa-devel in the future even if they are sent to the wrong
> personal email account of yours? I would assume that would only
> require a small change in your filter rules, not a change in your
> workflow.
I do look at the lists but it's very easy for things that only go there
to get missed and it's fairly low priority, the volume is very high and
obviously there's a lot of duplication from things that do land in my
inbox. Copying things into my inbox causes duplication problems due to
things going to lkml, lakml and subsystem specific lists and alsa-devel
being moderated for non-subscribers and subject mangling doesn't help
anything.
What's more likely to happen is that I just start ignoring the work
policy which is something I've been considering anyway.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140704/8ac9d058/attachment.sig>
prev parent reply other threads:[~2014-07-04 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 7:47 ASoC: samsung: MACH_SMDK6450 Paul Bolle
2014-07-02 9:23 ` Mark Brown
2014-07-02 22:37 ` Kukjin Kim
2014-07-03 11:14 ` Mark Brown
2014-07-04 0:39 ` Kukjin Kim
2014-07-04 3:39 ` Olof Johansson
2014-07-04 9:01 ` Arnd Bergmann
2014-07-04 11:45 ` Mark Brown [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=20140704114505.GA19453@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).