From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] MAINTAINERS: demote ARM port to "odd fixes"
Date: Mon, 26 Mar 2018 14:49:36 -0700 [thread overview]
Message-ID: <20180326144936.44f11e7105b8536ada593a6c@linux-foundation.org> (raw)
In-Reply-To: <CAKv+Gu-pgj_T6NC9==TjbbAZ0cgZkf6dQKi0AyQBHEGnzYGQBw@mail.gmail.com>
On Sun, 25 Mar 2018 19:41:49 +0100 Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> Nobody is asking you to prioritise voluntary work over paid work. I am
> asking you to consider offloading some of the responsibility to others
> if you are failing to cope by yourself.
That's a sensible proposal and it can be discussed in the appropriate
venue at an appropriate time (if it is found that we actually have a
problem!).
But all of this seems unrelated to altering the MAINTAINERS file today,
so I'll scoop up Russell's patches.
prev parent reply other threads:[~2018-03-26 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 15:02 [PATCH 2/2] MAINTAINERS: demote ARM port to "odd fixes" Russell King
2018-03-25 7:27 ` Ard Biesheuvel
2018-03-25 18:09 ` Russell King - ARM Linux
2018-03-25 18:41 ` Ard Biesheuvel
2018-03-26 21:49 ` Andrew Morton [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=20180326144936.44f11e7105b8536ada593a6c@linux-foundation.org \
--to=akpm@linux-foundation.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).