From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: ASoC: samsung: MACH_SMDK6450
Date: Fri, 04 Jul 2014 11:01:52 +0200 [thread overview]
Message-ID: <4203198.qV4EZfpui2@wuerfel> (raw)
In-Reply-To: <CAOesGMjdVrOfyrF6X3KoMQxBBYzNZskUsaMaHH653LJgwqpA+Q@mail.gmail.com>
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 Brown wrote:
> >>
> >> On Thu, Jul 03, 2014 at 07:37:07AM +0900, Kukjin Kim wrote:
> >> > On 07/02/14 18:23, Mark Brown wrote:
> >>
> >> > >This also wasn't sent to me for review, please always send patches to
> >> > >maintainers.
> >>
> >> > Mark, I always send patches to regarding maintainers and in this case the
> >> > patch missed the change. I'm resending new patch and if any problems, please
> >> > let me know. Just note, I just wanted to check whether there is no problem
> >> > with other maintainers' tree early in -next tree.
> >>
> >> It looks like you've sent it to broonie at linaro.org not broonie at kernel.org
> >> which is listed in MAINTAINERS and what I use for e-mail - upstream mail
> >> that goes to my work address often just gets dropped on the floor (and
> >> generally ends up at the bottom of my queue to look at) since it ends up
> >> in a completely different place to my personal mail.
> >
> > Mark, oh, I see. But I checked your e-mail address from recent your sign-off
> > in git commit so, just thought it should be fine.
> >
> > I will use kernel.org for your e-mail address next time
>
> 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.
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).
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.
Arnd
next prev parent reply other threads:[~2014-07-04 9:01 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 [this message]
2014-07-04 11:45 ` 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=4203198.qV4EZfpui2@wuerfel \
--to=arnd@arndb.de \
--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).