From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-iio@vger.kernel.org, linux-pm@vger.kernel.org,
Sebastian Reichel <sre@kernel.org>,
dri-devel@lists.freedesktop.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dan Murphy <dmurphy@ti.com>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee.jones@linaro.org>,
linux-leds@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: move Milo Kim to credits
Date: Tue, 22 Sep 2020 09:36:37 +0000 [thread overview]
Message-ID: <20200922093637.GK4792@sirena.org.uk> (raw)
In-Reply-To: <CAJKOXPdwQc86H-S=C4v_1VCbd7RhC2Soepj_2LqG1e_E_bgAug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Tue, Sep 22, 2020 at 09:08:37AM +0200, Krzysztof Kozlowski wrote:
> On Mon, 21 Sep 2020 at 23:06, Pavel Machek <pavel@ucw.cz> wrote:
> > I believe normal way would be to mark the entries "orphaned", not to
> > drop them altogether. Plus, I believe someone from TI is likely to
> > step up.
> These are entries for specific drivers so they are covered by the
> subsystem maintainers. You believe someone will step up, I believe if
> these were important for TI, they would find the person some time ago,
> so the emails won't bounce... This was similar with BQ chargers where
It's fairly common for mobile parts to get dropped relatively quickly as
the technology moves fairly quickly in that market, I think a lot of teh
parts that Milo was working on were mobile ones.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-22 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 21:02 [PATCH] MAINTAINERS: move Milo Kim to credits Krzysztof Kozlowski
2020-09-21 21:06 ` Pavel Machek
2020-09-22 7:08 ` Krzysztof Kozlowski
2020-09-22 9:36 ` Mark Brown [this message]
2020-09-22 11:36 ` Dan Murphy
2020-09-22 11:45 ` Krzysztof Kozlowski
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=20200922093637.GK4792@sirena.org.uk \
--to=broonie@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.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).